Re: [Distutils] Availability of setuptools installer for python2.6?
At 10:25 PM 10/6/2008 +0100, Paul Moore wrote:
2008/10/6 Phillip J. Eby <pje@telecommunity.com>:
At 12:05 PM 10/6/2008 -0700, Chris Mahan wrote:
Phillip,
At
<http://pypi.python.org/pypi/setuptools>http://pypi.python.org/pypi/setuptools
there is no MS windows installer for python 2.6.
Do you have an idea of when that might be available?
No, it'll likely be a while before I'm doing anything with 2.6. Ian Bicking now has privs for the setuptools PyPI entry, so perhaps he could upload one. (There actually isn't anything Windows-specific about it; all the .exe installers that I upload are actually built on a Linux machine.)
This is a really frustrating aspect of setuptools, that pure-Python packages produce version-specific installers.
Actually, that's not setuptools' fault in this case; I specifically make the .exe's version-specific because they have different contents. Different versions of Python include different distutils commands, and setuptools needs to install different things. So even though it's "pure" Python (ha!) it is still Python-version specific.
I'm sure I've seen an explanation of why this is necessary somewhere before, but I can't recall precisely where (and I don't really have time to wade through all the setuptools documentation to see if it's in there - it wasn't obvious from reading the contents). Can anyone give me a quick pointer to the explanation?
Eggs contain bytecode, and bytecode is Python version-specific.
2008/10/7 Phillip J. Eby <pje@telecommunity.com>:
This is a really frustrating aspect of setuptools, that pure-Python packages produce version-specific installers.
Actually, that's not setuptools' fault in this case; I specifically make the .exe's version-specific because they have different contents. Different versions of Python include different distutils commands, and setuptools needs to install different things. So even though it's "pure" Python (ha!) it is still Python-version specific.
Not sure I follow this. I see this in bdist_wininst installers, so distutils commands shouldn't be relevant (?) But I'll freely admit I'm naive over this stuff, so if I need to be enlightened, please do so!
Eggs contain bytecode, and bytecode is Python version-specific.
bdist_wininst recompiles bytecode at install-time, so that's not relevant for me. I can see it would be for eggs, but I'm talking about installers, here. Hmm, I just went looking for a specific example, and I see that the one I thought I remembered, Genshi, includes some C code I'd missed. Maybe I'm misinterpreting what I thought I'd seen. But I do wish people would continue to distribute bdist_wininst installers for pure python packages, rather than just version-specific .egg files. Never mind. We've done this discussion to death in the past. Let's just say that the move from bdist_wininst to eggs in some areas, is making an early switch to Python 2.6 harder for me on Windows than the equivalent switch to 2.5 was... Paul.
participants (2)
-
Paul Moore -
Phillip J. Eby