Thread: Python 2.7
View Single Post
Old 12-17-2010, 09:19 AM   #1
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,708
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Python 2.7

The change log indicates that the Windows binary build has been updated to use Python 2.7 (as of 0.7.30), but it's a little unclear (or I just missed it) if the Linux and OS X builds are now on 2.7, as well. (and if so... at what point) .

The reason I ask is that I have plugins that import compiled modules which may squawk about 'magic numbers' when importing modules from an older python build into a newer one.

I don't foresee much trouble handling the situation programmatically, but I need to verify if all three OS builds were switched to Python 2.7 at the same time... or if not, when.

Thanks
DiapDealer is offline   Reply With Quote