Re: [TIP] Anyone still using Python 2.5?
On Wed, Dec 21, 2011 at 1:15 AM, Chris Withers ch...@simplistix.co.ukwrote: Hi All, What's the general consensus on supporting Python 2.5 nowadays? If you compile mod_wsgi with Apache you are stuck on the version of Python you compiled with. I had an old server stuck on Python 2.5 for this reason but I finally got a new box where I will be stuck on Python 2.7 for a while. There's probably a better way with gunicorn or something but Apache is pretty sweet when you configure it right. btw, tox is great for developing a project that supports multiple Pythons: http://tox.testrun.org/latest/ Do people still have to use this in commercial environments or is everyone on 2.6+ nowadays? I'm finally getting some continuous integration set up for my packages and it's highlighting some 2.5 compatibility issues. I'm wondering whether to fix those (lots of ugly from __future__ import with_statement everywhere) or just to drop Python 2.5 support. What do people feel? cheers, Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk __**_ testing-in-python mailing list testing-in-python@lists.idyll.**org testing-in-pyt...@lists.idyll.org http://lists.idyll.org/**listinfo/testing-in-pythonhttp://lists.idyll.org/listinfo/testing-in-python -- http://mail.python.org/mailman/listinfo/python-list
Anyone still using Python 2.5?
Hi All, What's the general consensus on supporting Python 2.5 nowadays? Do people still have to use this in commercial environments or is everyone on 2.6+ nowadays? I'm finally getting some continuous integration set up for my packages and it's highlighting some 2.5 compatibility issues. I'm wondering whether to fix those (lots of ugly from __future__ import with_statement everywhere) or just to drop Python 2.5 support. What do people feel? cheers, Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk -- http://mail.python.org/mailman/listinfo/python-list
Re: Anyone still using Python 2.5?
Chris Withers, 21.12.2011 08:15: What's the general consensus on supporting Python 2.5 nowadays? From my own (recent) polls, it appears that people want continued support for Python 2.4 and later for a couple of years to come, mainly because RHEL5 uses that by default and has official support until 2014. Similar considerations apply to many Solaris installations. The general consensus seems to be that support for Python 2.3 can easily be dropped, but that support for Py2.4 and later would be helpful. Stefan -- http://mail.python.org/mailman/listinfo/python-list
Re: [TIP] Anyone still using Python 2.5?
On Wed, Dec 21, 2011 at 07:15:46AM +, Chris Withers wrote: Hi All, What's the general consensus on supporting Python 2.5 nowadays? Do people still have to use this in commercial environments or is everyone on 2.6+ nowadays? I'm finally getting some continuous integration set up for my packages and it's highlighting some 2.5 compatibility issues. I'm wondering whether to fix those (lots of ugly from __future__ import with_statement everywhere) or just to drop Python 2.5 support. What do people feel? Most linux distribution went directly from 2.4 to 2.5 Debian: old stable (lenny) 2.4 stable (squeeze)2.5 Red Hat REHL5 2.4 REHL6 2.6 The most notable exception is Ubuntu Hardy and LTS release from april 2008 with 2.5. But this LTS is out of support for almost 1 year now and current LTS (Lucid) ship 2.6. If you don't plan to support 2.4, supporting 2.5 does not seems a priority. -- Pierre-Yves David http://www.logilab.fr/ signature.asc Description: Digital signature -- http://mail.python.org/mailman/listinfo/python-list
RE: [TIP] Anyone still using Python 2.5?
We've a bunch of windows servers stuck on python 2.5 since an API we use on them is shipped to us pyc's only - forcing us to stay with that version. Most of our other machines are on 2.6 or 2.7. -Original Message- From: testing-in-python-boun...@lists.idyll.org [mailto:testing-in-python-boun...@lists.idyll.org] On Behalf Of Chris Withers Sent: 21 December 2011 07:16 To: Python List; testing-in-pyt...@lists.idyll.org; simplis...@googlegroups.com Subject: [TIP] Anyone still using Python 2.5? Hi All, What's the general consensus on supporting Python 2.5 nowadays? Do people still have to use this in commercial environments or is everyone on 2.6+ nowadays? I'm finally getting some continuous integration set up for my packages and it's highlighting some 2.5 compatibility issues. I'm wondering whether to fix those (lots of ugly from __future__ import with_statement everywhere) or just to drop Python 2.5 support. What do people feel? cheers, Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk ___ testing-in-python mailing list testing-in-pyt...@lists.idyll.org http://lists.idyll.org/listinfo/testing-in-python ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 ** -- http://mail.python.org/mailman/listinfo/python-list
Re: Anyone still using Python 2.5?
On Wed, 21 Dec 2011 07:15:46 +, Chris Withers wrote: Hi All, What's the general consensus on supporting Python 2.5 nowadays? Do people still have to use this in commercial environments or is everyone on 2.6+ nowadays? Centos and Red Hat production systems still use Python 2.4, so yes, absolutely, 2.5 and 2.4 still need to be supported. Not necessarily by package authors though -- that's a matter for them to decide. I'm presently writing a small library which will support 2.4 through 3.2, which isn't as hard as it sounds like, but still isn't exactly fun. If the project were much bigger, I'd drop support for 2.4 and only support 2.5. At least then I could use conditional expressions and __future__ imports. I'm finally getting some continuous integration set up for my packages and it's highlighting some 2.5 compatibility issues. I'm wondering whether to fix those (lots of ugly from __future__ import with_statement everywhere) or just to drop Python 2.5 support. What do people feel? It really depends on *your* users, not arbitrary developers. How many of your users are using 2.5? -- Steven -- http://mail.python.org/mailman/listinfo/python-list
Re: [TIP] Anyone still using Python 2.5?
On Wed, Dec 21, 2011 at 9:21 AM, Pierre-Yves David pierre-yves.da...@logilab.fr wrote: ... The most notable exception is Ubuntu Hardy and LTS release from april 2008 with 2.5. But this LTS is out of support for almost 1 year now and current LTS (Lucid) ship 2.6. Not quite. Ubuntu 8.04 LTS is supported on the server until April 2013. jml -- http://mail.python.org/mailman/listinfo/python-list
Re: [TIP] Anyone still using Python 2.5?
On Wed, Dec 21, 2011 at 2:15 AM, Chris Withers ch...@simplistix.co.uk wrote: Hi All, What's the general consensus on supporting Python 2.5 nowadays? Do people still have to use this in commercial environments or is everyone on 2.6+ nowadays? I'm finally getting some continuous integration set up for my packages and it's highlighting some 2.5 compatibility issues. I'm wondering whether to fix those (lots of ugly from __future__ import with_statement everywhere) or just to drop Python 2.5 support. What do people feel? Google app engine is still Python 2.5, as is Jython. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton -- http://mail.python.org/mailman/listinfo/python-list
Re: Anyone still using Python 2.5?
Em quarta-feira, 21 de dezembro de 2011 08:50:34, Steven D'Aprano escreveu: On Wed, 21 Dec 2011 07:15:46 +, Chris Withers wrote: Hi All, What's the general consensus on supporting Python 2.5 nowadays? Do people still have to use this in commercial environments or is everyone on 2.6+ nowadays? Centos and Red Hat production systems still use Python 2.4, so yes, absolutely, 2.5 and 2.4 still need to be supported. Not necessarily by package authors though -- that's a matter for them to decide. I'm presently writing a small library which will support 2.4 through 3.2, which isn't as hard as it sounds like, but still isn't exactly fun. If the project were much bigger, I'd drop support for 2.4 and only support 2.5. At least then I could use conditional expressions and __future__ imports. I'm finally getting some continuous integration set up for my packages and it's highlighting some 2.5 compatibility issues. I'm wondering whether to fix those (lots of ugly from __future__ import with_statement everywhere) or just to drop Python 2.5 support. What do people feel? It really depends on *your* users, not arbitrary developers. How many of your users are using 2.5? There are still people on 2.5. ESRIs customers (www.esri.com) that rely heavily on Python 2.5, because it ships with a popular ArcGIS release (9.31). The new ArcGIS release uses 2.6, but I can see 9.31 lurking around for another year, at least. Cheers. -- http://mail.python.org/mailman/listinfo/python-list
Re: Anyone still using Python 2.5?
In article 4ef1b9fa$0$29973$c3e8da3$54964...@news.astraweb.com, Steven D'Aprano steve+comp.lang.pyt...@pearwood.info wrote: Centos and Red Hat production systems still use Python 2.4, so yes, absolutely, 2.5 and 2.4 still need to be supported. Is Python 2.4 destined to be the next IE-6? -- http://mail.python.org/mailman/listinfo/python-list
Re: [TIP] Anyone still using Python 2.5?
On Dec 21, 2011, at 2:15 AM, Chris Withers ch...@simplistix.co.uk wrote: Hi All, What's the general consensus on supporting Python 2.5 nowadays? Do people still have to use this in commercial environments or is everyone on 2.6+ nowadays? For those of us living the nightmare of AppEngine *and* working on an app old enough to not be using the newer Datastore, we're stuck on 2.5 until we can justify a data migration. Frankly I don't know how many such apps exist these days that are still actively developed, though. I'm finally getting some continuous integration set up for my packages and it's highlighting some 2.5 compatibility issues. I'm wondering whether to fix those (lots of ugly from __future__ import with_statement everywhere) or just to drop Python 2.5 support. What do people feel? cheers, Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk ___ testing-in-python mailing list testing-in-pyt...@lists.idyll.org http://lists.idyll.org/listinfo/testing-in-python -- http://mail.python.org/mailman/listinfo/python-list
Re: [TIP] Anyone still using Python 2.5?
In article mailman.3913.1324474710.27778.python-l...@python.org, Tom Davis t...@recursivedream.com wrote: For those of us living the nightmare of AppEngine I've never used AppEngine, just read a little about it. Could you explain why it's a nightmare? -- http://mail.python.org/mailman/listinfo/python-list
Re: Anyone still using Python 2.5?
On 12/21/11 07:07, Roy Smith wrote: In article4ef1b9fa$0$29973$c3e8da3$54964...@news.astraweb.com, Steven D'Apranosteve+comp.lang.pyt...@pearwood.info wrote: Centos and Red Hat production systems still use Python 2.4, so yes, absolutely, 2.5 and 2.4 still need to be supported. Is Python 2.4 destined to be the next IE-6? No...unlike IE6, 2.4 backwards compatibility has a foreseeable death when RHEL+2.6 eventually fall out of support ;-) -tkc -- http://mail.python.org/mailman/listinfo/python-list
Re: [TIP] Anyone still using Python 2.5?
On 2011-12-21T07:15:46+, Chris Withers wrote: Hi All, What's the general consensus on supporting Python 2.5 nowadays? Do people still have to use this in commercial environments or is everyone on 2.6+ nowadays? 2.5, how modern. SUSE Linux Enterprise Server 10 comes with 2.4.2 Will be moving to a RHEL derivative running 2.6, though. The conservative enterprise will probably run py3k by y3k. :-( -- Chris pgpQUloG0TcPC.pgp Description: PGP signature -- http://mail.python.org/mailman/listinfo/python-list
Re: [TIP] Anyone still using Python 2.5?
On Wed, Dec 21, 2011 at 05:57, Jim Fulton j...@zope.com wrote: On Wed, Dec 21, 2011 at 2:15 AM, Chris Withers ch...@simplistix.co.uk wrote: Hi All, What's the general consensus on supporting Python 2.5 nowadays? Do people still have to use this in commercial environments or is everyone on 2.6+ nowadays? I'm finally getting some continuous integration set up for my packages and it's highlighting some 2.5 compatibility issues. I'm wondering whether to fix those (lots of ugly from __future__ import with_statement everywhere) or just to drop Python 2.5 support. What do people feel? Google app engine is still Python 2.5, as is Jython. But App Engine also supports Python 2.7: http://code.google.com/appengine/docs/python/python27/ (currently experimental, but then again App Engine itself was in preview mode until just this past month). -- http://mail.python.org/mailman/listinfo/python-list
Re: [TIP] Anyone still using Python 2.5?
On Wed, Dec 21, 2011 at 2:57 AM, Jim Fulton j...@zope.com wrote: On Wed, Dec 21, 2011 at 2:15 AM, Chris Withers ch...@simplistix.co.uk wrote: Hi All, What's the general consensus on supporting Python 2.5 nowadays? Do people still have to use this in commercial environments or is everyone on 2.6+ nowadays? I'm finally getting some continuous integration set up for my packages and it's highlighting some 2.5 compatibility issues. I'm wondering whether to fix those (lots of ugly from __future__ import with_statement everywhere) or just to drop Python 2.5 support. What do people feel? Google app engine is still Python 2.5, as is Jython. There's work being done to change that on the app engine front: http://code.google.com/appengine/docs/python/python27/newin27.html -gps -- http://mail.python.org/mailman/listinfo/python-list
Re: [TIP] Anyone still using Python 2.5?
Just because the default python version on a server is 2.4 doesn't mean you can't install 2.7.2... If the admins that run the machine are too lazy/stupid to install a second copy of Python let them rot. Of course, if by some nightmare scenario you have code that can't be upgraded for whatever reason, I'm so sorry. Nathan -- http://mail.python.org/mailman/listinfo/python-list
Re: [TIP] Anyone still using Python 2.5?
On Wed, 21 Dec 2011 21:15:31 -0500, Nathan Rice wrote: Just because the default python version on a server is 2.4 doesn't mean you can't install 2.7.2... If the admins that run the machine are too lazy/stupid to install a second copy of Python let them rot. If any of my sys admins installed non-supported software on one of my production servers without permission, they'd be looking for a new job. Just because some guy with root privileges can install software doesn't mean that he should. Having vendor support and security patches is far more important than the ability to write one-liner if statements. -- Steven -- http://mail.python.org/mailman/listinfo/python-list
Re: Anyone still using Python 2.5?
Dennis Lee Bieber, 21.12.2011 17:48: On Wed, 21 Dec 2011 07:15:46 +, Chris Withers wrote: What's the general consensus on supporting Python 2.5 nowadays? Do people still have to use this in commercial environments or is everyone on 2.6+ nowadays? I was recently laid-off from a program that is still using Python 2.3 [...] That reminds me: we shouldn't forget about embedded Python installations. They are usually somewhere between very hard and impossible to upgrade, also because they often use vendor supplied binary packages for plugin APIs. I've recently seen that in a FrontArena installation (basically a trading platform) that had an embedded Py2.3 for scripting. It wasn't exactly the cutting-edge release, but the users of these platforms tend to be pretty conservative with their upgrades, and the time it takes the vendor to upgrade to a new embedded Python version can be similarly long. That means it can take several years before an embedded 2.7 hits the end users, during which anything can happen, from vendor switches from Python to Lua to vendor goes bankrupt (or maybe just one after the other). Stefan -- http://mail.python.org/mailman/listinfo/python-list
Re: using python 2.5
kunal.k wrote: I have installed python 2.5 for a particular code. Now i have 2.6 already installed. How do i direct this code to use the 2.5 modules?? I can think of two different questions you might be asking. 1) How do I get the add-on modules installed with 2.6 to also work in 2.5? or 2) How do I get a particular script to use 2.5, while all other scripts should use 2.6 ? Sean answered #1, but I think you meant to ask #2 First question is what OS you've installed these on. In Windows, the python version is selected by file associations, while in Unix/Linux systems, it's selected by the shebang line at the beginning of the script. A generic answer if you just have one script is to make an OS script (bat file, or shell script) that invokes the particular python interpreter, passing it the script name as an argument). But if you want to be able to just run the script as though it were a compiled executable, tell us what OS you're on, and maybe the base locations of your two installations. DaveA -- http://mail.python.org/mailman/listinfo/python-list
using python 2.5
I have installed python 2.5 for a particular code. Now i have 2.6 already installed. How do i direct this code to use the 2.5 modules?? -- http://mail.python.org/mailman/listinfo/python-list
Re: using python 2.5
On Sep 21, 4:42 pm, kunal.k kunalker...@gmail.com wrote: I have installed python 2.5 for a particular code. Now i have 2.6 already installed. How do i direct this code to use the 2.5 modules?? I don't think you do. You should install the modules for python 2.6. You could try to hand copy the modules, and some might work, but it's crap shoot. ~Sean -- http://mail.python.org/mailman/listinfo/python-list
Re: anybody using python 2.5 that raises error while importing?
John Machin wrote: daniel wrote: there's a dll extension used to be imported with no error under version 2.4.3, but the new python complains that the name of the module can't be found. seems not mentioned in the official documentation, any work around to fix the issue without switching back to the old version? thank you for your reply.. Did/does its name end in .dll or in .pyd? It ends in .dll Have you procured a new one (necessary when there's a change of minor version number) and installed it in the right place? My output of python -V shows 2.5c2 Can you tell us the name of the module, and the path to the DLL/PYD The dll is distributed with a third party library, it claimed to be compatible with 2.4, It was installed at d:\ on my box, and the path had been added to my PYTHONPATH variable. that is/was imported by Python 2.4? yep, it works very well with python 2.4, so, I'm just wondering if there is a fix for using with 2.5 Have you contacted the author(s) of the module? uh.. not yet, because they clearly mentioned that in the doc. Have you installed Python 2.5 in its own directory e.g. c:\python25 (the default)? Python 2.4, same question? Have you uninstalled 2.4? I already uninstalled the version 2.4. and put python25 in drive d:. there's probably no problem with my environment variables, maybe I should check for a updated version of python. thanks again. daniel Regards, John -- http://mail.python.org/mailman/listinfo/python-list
Re: anybody using python 2.5 that raises error while importing?
daniel wrote: John Machin wrote: daniel wrote: there's a dll extension used to be imported with no error under version 2.4.3, but the new python complains that the name of the module can't be found. seems not mentioned in the official documentation, any work around to fix the issue without switching back to the old version? thank you for your reply.. Did/does its name end in .dll or in .pyd? It ends in .dll Have you procured a new one (necessary when there's a change of minor version number) and installed it in the right place? My output of python -V shows 2.5c2 Huh? The question was in effect Have you obtained a NEW version of the *DLL*? This is necessary when you upgrade from Python 2.4 to Python 2.5. Can you tell us the name of the module, and the path to the DLL/PYD The dll is distributed with a third party library, it claimed to be compatible with 2.4, It was installed at d:\ on my box, and the path had been added to my PYTHONPATH variable. Do you mean that the full path to the module was d:\the_module_name.dll ? that is/was imported by Python 2.4? yep, it works very well with python 2.4, so, I'm just wondering if there is a fix for using with 2.5 No, you can't use a 2.4-compatible binary module with 2.5. Have you contacted the author(s) of the module? uh.. not yet, because they clearly mentioned that in the doc. They clearly mentioned *what* in the doc? Have they yet announced availibility of a 2.5-supported version of their software? Have you installed Python 2.5 in its own directory e.g. c:\python25 (the default)? Python 2.4, same question? Have you uninstalled 2.4? I already uninstalled the version 2.4. and put python25 in drive d:. there's probably no problem with my environment variables, maybe I should check for a updated version of python. Huh, again? Firstly, 2.5 final has been released -- you should really subscribe to the python-announce mailing list so that you don't need to check for major events. Secondly, upgrading from 2.5c2 to 2.5 is generally a good thing, but it won't solve your missing dll problem. From 2.5 onwards, a Python extension module must be named .pyd, it can't be named .dll. You could try renaming it, but you are likely to get this error when you try to import it in 2.5: ImportError: Module use of python24.dll conflicts with this version of Python. IOW, the version compatibility problem. Bottom line: you need to get an updated extension module from the software supplier. HTH, John -- http://mail.python.org/mailman/listinfo/python-list
Re: anybody using python 2.5 that raises error while importing?
thank you so much for your help.. I've got no idea about pyd or dll stuff, started to learn python just several weeks ago. so the implementation rules of python extension module must have been changed, for now, I have to wait for the new release of that module and switch back to python 2.4 to get my work done. thanks again.. daniel -- http://mail.python.org/mailman/listinfo/python-list
Re: anybody using python 2.5 that raises error while importing?
Dennis Lee Bieber schrieb: On 23 Sep 2006 09:24:09 -0700, daniel [EMAIL PROTECTED] declaimed the following in comp.lang.python: so the implementation rules of python extension module must have been changed, for now, I have to wait for the new release of that module and No change... For YEARS the rule has been: Changes in the first decimal place (version m.n.o - if n changes, new binaries are needed; changes in o are just bug fixes and don't change the binary interface; abandon all hope if m changes G) of a Python version almost ALWAYS require 3rd party binary extensions to be rebuilt. You should read the entire thread. He couldn't import the extension module because it ends in .dll; this was a change introduced in Python 2.5: the module must end in .pyd now. That rule had not been there for YEARS. Of course, had he renamed the file, it then would have complained that he's running a 2.4 extension module in 2.5; *that* rule had been there for YEARS. Regards, Martin -- http://mail.python.org/mailman/listinfo/python-list
anybody using python 2.5 that raises error while importing?
there's a dll extension used to be imported with no error under version 2.4.3, but the new python complains that the name of the module can't be found. seems not mentioned in the official documentation, any work around to fix the issue without switching back to the old version? tks.. daniel -- http://mail.python.org/mailman/listinfo/python-list
Re: anybody using python 2.5 that raises error while importing?
daniel wrote: there's a dll extension used to be imported with no error under version 2.4.3, but the new python complains that the name of the module can't be found. seems not mentioned in the official documentation, any work around to fix the issue without switching back to the old version? Did/does its name end in .dll or in .pyd? Have you procured a new one (necessary when there's a change of minor version number) and installed it in the right place? Can you tell us the name of the module, and the path to the DLL/PYD that is/was imported by Python 2.4? Have you contacted the author(s) of the module? Have you installed Python 2.5 in its own directory e.g. c:\python25 (the default)? Python 2.4, same question? Have you uninstalled 2.4? Regards, John -- http://mail.python.org/mailman/listinfo/python-list
