New submission from Jeroen Ruigrok van der Werven [EMAIL PROTECTED]:
Currently eggs created for amd64 platforms are called x86_64 in the egg
filename. AMD renamed x86_64 to amd64 and asked people to follow suit.
Also Python uses the amd64 nomenclature:
New submission from Jeroen Ruigrok van der Werven [EMAIL PROTECTED]:
As I explained in
http://mail.python.org/pipermail/distutils-sig/2008-April/009398.html eggs
created on either a 32- or 64-bits Windows call the resulting file only a win32
egg.
For pure Python modules this is not an issue.
-On [20080508 10:37], Jeff Rush ([EMAIL PROTECTED]) wrote:
We now have a specific issues tracker for setuptools at:
http://bugs.python.org/setuptools/
Thanks Jeff, I've taken the liberty to seed it with 3 issues already. ^^
--
Jeroen Ruigrok van der Werven asmodai(-at-)in-nomine.org
New submission from Jeroen Ruigrok van der Werven [EMAIL PROTECTED]:
As I reported in
http://mail.python.org/pipermail/distutils-sig/2008-April/009398.html
easy_install on a 64 bits Python on a 64 bits Windows is broken in that it gives
the following error:
Cannot find Python executable
We now have a specific issues tracker for setuptools at:
http://bugs.python.org/setuptools/
and
[EMAIL PROTECTED] (for email issue postings)
using the Roundup tracker software also used for Python bug tracking.
Note that the trailing slash is NOT optional. For now the tracker echoes
Currently eggs created for amd64 platforms are called x86_64 in the egg
filename. AMD renamed x86_64 to amd64 and asked people to follow suit.
Also Python uses the amd64 nomenclature:
http://mail.python.org/pipermail/python-bugs-list/2006-
December/036400.html and
New submission from Jeff Kowalczyk [EMAIL PROTECTED]:
When I upgraded to subversion-1.5, working copies using various combinations of
virtualenv, zc.buildout, setuptools all stopped working with errors similar to
the following:
python: /opt/python24/python/bin/python
virtualenv (svn trunk)
On May 8, 2008, at 2:40 AM, Jeff Rush wrote:
We now have a specific issues tracker for setuptools at:
http://bugs.python.org/setuptools/
Thank you very much, Jeff!
I've added a note to the front page of my setuptools issue tracker
asking people to use the official one insteda:
-On [20080508 10:37], Jeff Rush ([EMAIL PROTECTED]) wrote:
We now have a specific issues tracker for setuptools at:
http://bugs.python.org/setuptools/
Can we get a patch keyword?
--
Jeroen Ruigrok van der Werven asmodai(-at-)in-nomine.org / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in
New submission from Jeroen Ruigrok van der Werven [EMAIL PROTECTED]:
Setuptools currently uses the module md5, which will be deprecated after 2.6 and
2.6 warns about this use.
Find attached a patch I emailed to Phillip a while ago but still did not get
applied.
--
messages: 6
nosy:
2008/5/8 Jeff Rush [EMAIL PROTECTED]:
Note that the trailing slash is NOT optional. For now the tracker echoes
bug reports onto the distutils list, for community awareness. If this turns
out to be a problem, I'll create a separate distutils-bugs list but wanted
to avoid having folks sign up
New submission from Peter Fein [EMAIL PROTECTED]:
Setuptools installs all files with mode +x (executable), overriding any
permissions specified in the original archive. The consensus on the distutils
mailing list is that doing so is incorrect, and potentially dangerous. It also
breaks
Peter Fein wrote:
Setuptools installs all files with mode +x (executable), overriding any
permissions specified in the original archive.
ALL files? Literally?
If that's true, then on Unix this is astonishingly
wrong and definitely needs to be fixed.
--
Greg
On May 8, 2008, at 11:29 PM, Greg Ewing wrote:
Peter Fein wrote:
Setuptools installs all files with mode +x (executable), overriding
any permissions specified in the original archive.
ALL files? Literally?
All .py/.pyc files, yes.
If that's true, then on Unix this is astonishingly
14 matches
Mail list logo