Re: [python-win32] Next question relating to 'better' versions
Cool. Thanks. I think that for now, until they maybe confirm that the plugins they'd want to include for actual use won't work with it, etc., I'll just stick to 3.2, and will also worry about turning it into standalone executables at a later stage since that's not really an issue either at this stage - more related to me just thinking about passing some small apps on to various guys who might not have python installed as such at some stage. For now am really just trying to get relatively comfortable with any syntax differences from other environments etc. have worked in the most recently (C# and PHP, and javascript), but will also just say that my one irritation with most languages has always been what I would describe as array content management, and I am so far quite impressed with python handling all it's different types of sequential data object handling, etc. - hope that terminology isn't too far off, but mean things like list, tuple, dictionary objects, etc. etc., and I do also quite like the polymorphism of object/variable types, but along with their built-in function handling/attachment. Stay well Jacob Kruger Blind Biker Skype: BlindZA '...fate had broken his body, but not his spirit...' - Original Message ------- Subject: Re: [python-win32] Next question relating to 'better' versions From: Tim Golden Date: Thu, 19 May 2011 14:15:58 +0100 To: Cc: python-win32@python.org >On 19/05/2011 10:22, Jacob Kruger wrote: >> Ok, firstly, I have moved over to an email address I do actually have >> some control over the format of, but anyway. > >Thanks for doing that -- it does make a difference to those >of us reading the result :) > >[... Which version of Python? ...] > >It's a tricky one (sometimes) and an amount is determined by what >libraries or tools you want / need to use. You've mentioned py2exe >and Eclipse, and if the lack of those, for example, is a showstopper >then your decision is made. That said, PyDev (the Python "mode" for >Eclipse) does appear to support Python 3 (I can't find an outright >statement to that effect, but there are several mentions of Python3 >in their docs). Also, I don't about py2exe, but cx_freeze seems to >have versions for Python 3. > >But regardless of tools, there's the wider issue: which is better >to start off with? I think it's worth pointing out that, especially >if you're looking at 2.7 -- but even with earlier 2.x versions -- >there isn't *that* much difference. My wmi library runs >unaltered on versions from 2.4 to 3.3. I did have to make some >tiny compromises, but the point I'm making is that Python 3 is >*not* worlds away from Python 2. Whichever version you plump for >now, you'll be well-placed to use the other one if you ever need >to. > >General guidance would be: go with Python 3 if you're starting >afresh, unless you have some overriding need for a library or >tool which hasn't been ported (and which you can't easily port >yourself... it might be easier than you think). Another of my >libraries runs on both versions by virtue of running the 2to3.py >library across it on install. (The pywin32 extensions use the >same approach). > >TJG >___ >python-win32 mailing list >python-win32@python.org >http://mail.python.org/mailman/listinfo/python-win32 ___ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
Re: [python-win32] Next question relating to 'better' versions
On 19/05/2011 10:22, Jacob Kruger wrote: Ok, firstly, I have moved over to an email address I do actually have some control over the format of, but anyway. Thanks for doing that -- it does make a difference to those of us reading the result :) [... Which version of Python? ...] It's a tricky one (sometimes) and an amount is determined by what libraries or tools you want / need to use. You've mentioned py2exe and Eclipse, and if the lack of those, for example, is a showstopper then your decision is made. That said, PyDev (the Python "mode" for Eclipse) does appear to support Python 3 (I can't find an outright statement to that effect, but there are several mentions of Python3 in their docs). Also, I don't about py2exe, but cx_freeze seems to have versions for Python 3. But regardless of tools, there's the wider issue: which is better to start off with? I think it's worth pointing out that, especially if you're looking at 2.7 -- but even with earlier 2.x versions -- there isn't *that* much difference. My wmi library runs unaltered on versions from 2.4 to 3.3. I did have to make some tiny compromises, but the point I'm making is that Python 3 is *not* worlds away from Python 2. Whichever version you plump for now, you'll be well-placed to use the other one if you ever need to. General guidance would be: go with Python 3 if you're starting afresh, unless you have some overriding need for a library or tool which hasn't been ported (and which you can't easily port yourself... it might be easier than you think). Another of my libraries runs on both versions by virtue of running the 2to3.py library across it on install. (The pywin32 extensions use the same approach). TJG ___ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
[python-win32] Next question relating to 'better' versions
Ok, firstly, I have moved over to an email address I do actually have some control over the format of, but anyway. Aside from that, I was just wondering what versions of python would be better to actually get used to since while I am currently going through a 4th edition version of Learning Python, which is one of the books I ran across a mention of in the specific tutorial material I was looking at for Eclipse IDE etc. earlier since that's the sort of preferred IDE for some of the guys here at work who want to focus on a specific form of python development for a hand held device, but I see in that book they mention various version changes relating to some built in functions, slight syntax changes, etc., and, for example, while now looking into py2exe, I see that it currently is only meant to support up to around python 2.7 at the moment..? Another simple example was that while playing around at looking into something like a rather simple interactive fiction interpreter that was using to test various tutorial bits of material, I see that while in 3.2 I had been using the input() function, it does something a bit different if I then try execute that piece of scripting/coding via 2.7 or 2.6 - tries to do what 3.2 would call an eval() on it. That's still not the end of the world, but had currently been playing around with python 3.2 on my 2 different machines, but do also have 2.6 and 2.7 installed, but, for example, the environment variable's path variable currently refers to python 3.2, but anyway - just wondering if it's better to not rush into newer versions off-hand, since also think my boss mentioned 2.6 to me or something? Stay well Jacob Kruger Blind Biker Skype: BlindZA '...fate had broken his body, but not his spirit...' ___ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
