On 3 June 2013 11:47, Chris “Kwpolska” Warrick <kwpol...@gmail.com> wrote: > >> Ah, question just came up. Since I have two pys, when a module is >> ported from 2.7 to 3.2 does it always have a different name? > > It never does. And in case it does, the developers are idiots.
Using Python 2.7 on Windows 7 So to clarify, the module names are the same on 2.7 and 3.3. Does that mean the module writers set the module so it will only install on the proper Py version, failing if it can't find it, so I don't have to think about that? Incidentally, for those nutty enough to run two Pys on Win, with Wing 101, I realized you can get Wing 101 to run either, without having to reconfigure it all the time, by setting up a Guest account in Windows, and configuring the second Wing for Py 3.3, run as Guest, with the primary as 2.7. This is helpful since some online sources I read are for one Py and some are for another. Jim _______________________________________________ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: http://mail.python.org/mailman/listinfo/tutor
