[Distutils] [issue1] amd64 eggs are called x86_64
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: http://mail.python.org/pipermail/python-bugs-list/2006-December/036400.html and http://mail.python.org/pipermail/python-dev/2008-May/079056.html As such, to limit end-user confusion eggs should be named amd64 as well instead of x86_64. -- messages: 1 nosy: asmodai priority: bug status: unread title: amd64 eggs are called x86_64 ___ Setuptools tracker [EMAIL PROTECTED] http://bugs.python.org/setuptools/issue1 ___ ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
[Distutils] [issue3] eggs on Windows do not differentiate between 32- or 64-bits
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. However, when using speedups or other code that needs to be natively compiled (C source code for example) you generate specific binaries for either 32- or 64-bits. We already differentiate between these versions on Unix and as such we should do the same on Windows. Something like module-1.0-py2.5-win32-i386.egg or module-1.0-py2.5-win32-amd64.egg. -- messages: 3 nosy: asmodai priority: urgent status: unread title: eggs on Windows do not differentiate between 32- or 64-bits ___ Setuptools tracker [EMAIL PROTECTED] http://bugs.python.org/setuptools/issue3 ___ ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Issues Tracker for Setuptools
-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 / asmodai イェルーン ラウフロック ヴァン デル ウェルヴェン http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B If Winter comes, can Spring be far behind..? ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
[Distutils] [issue2] easy_install broken on 64 bits Windows
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 C:\Python25\python.exe I believe that due to cli.exe and gui.exe (built from launcher.c) being 32-bits executables they are trying to use 32-bit specific calls which fail on a 64 bits Windows. As Mark Hammond said in http://mail.python.org/pipermail/distutils-sig/2008-May/009462.html: I suspect that the issue is that a 32bit cli.exe or gui.exe is attempting to LoadLibrary a 64bit executable and failing (specifically, loadable_exe() in launcher.c) -- messages: 2 nosy: asmodai priority: urgent status: unread title: easy_install broken on 64 bits Windows ___ Setuptools tracker [EMAIL PROTECTED] http://bugs.python.org/setuptools/issue2 ___ ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
[Distutils] Issues Tracker for Setuptools
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 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 for yet-another-list if I would avoid it. -Jeff ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] [issue1] amd64 eggs are called x86_64
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 http://mail.python.org/pipermail/python-dev/2008-May/079056.html As such, to limit end-user confusion eggs should be named amd64 as well instead of x86_64. Note that win- should probably be in the filename too. eg, the py 2.6 trunk building pywin32 will create a filename 'pywin32-210.9.win-amd64-py2.6.exe' Cheers, Mark ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
[Distutils] [issue4] subversion 1.5 working copy causes problem in entries_finder: NameError: global name 'log' is not defined
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) activated
working copy: svn://svn.zope.org/repos/main/z3c.formdemo/trunk
virtualenv python bootstrap.py, .bin/buildout
try to upgrade setuptools to dev copy per PJE mailing list post:
(formdemo) /software/z3c/formdemo $ easy_install setuptools==dev06
Searching for setuptools==dev06
Reading http://pypi.python.org/simple/setuptools/
Best match: setuptools dev06
Downloading
http://svn.python.org/projects/sandbox/branches/setuptools-0.6/#egg=setuptools-dev06
Doing subversion checkout from
http://svn.python.org/projects/sandbox/branches/setuptools-0.6/ to
/tmp/easy_install-MKC07e/setuptools-0.6
Processing setuptools-0.6
Running setup.py -q bdist_egg --dist-dir
/tmp/easy_install-MKC07e/setuptools-0.6/egg-dist-tmp-izAnB2
unrecognized .svn/entries format; skipping .
Traceback (most recent call last):
File /software/z3c/formdemo/bin/easy_install, line 7, in ?
sys.exit(
File
/software/z3c/formdemo/lib/python2.4/site-packages/setuptools-0.6c8-py2.4.egg/setuptools/command/easy_install.py,
line 1671, in main
with_ei_usage(lambda:
File
/software/z3c/formdemo/lib/python2.4/site-packages/setuptools-0.6c8-py2.4.egg/setuptools/command/easy_install.py,
line 1659, in with_ei_usage
return f()
File
/software/z3c/formdemo/lib/python2.4/site-packages/setuptools-0.6c8-py2.4.egg/setuptools/command/easy_install.py,
line 1675, in lambda
distclass=DistributionWithoutHelpCommands, **kw
File /opt/python24/./python/lib/python2.4/distutils/core.py, line 149, in
setup
dist.run_commands()
File /opt/python24/./python/lib/python2.4/distutils/dist.py, line 946, in
run_commands
self.run_command(cmd)
File /opt/python24/./python/lib/python2.4/distutils/dist.py, line 966, in
run_command
cmd_obj.run()
File
/software/z3c/formdemo/lib/python2.4/site-packages/setuptools-0.6c8-py2.4.egg/setuptools/command/easy_install.py,
line 211, in run
self.easy_install(spec, not self.no_deps)
File
/software/z3c/formdemo/lib/python2.4/site-packages/setuptools-0.6c8-py2.4.egg/setuptools/command/easy_install.py,
line 446, in easy_install
return self.install_item(spec, dist.location, tmpdir, deps)
File
/software/z3c/formdemo/lib/python2.4/site-packages/setuptools-0.6c8-py2.4.egg/setuptools/command/easy_install.py,
line 476, in install_item
dists = self.install_eggs(spec, download, tmpdir)
File
/software/z3c/formdemo/lib/python2.4/site-packages/setuptools-0.6c8-py2.4.egg/setuptools/command/easy_install.py,
line 655, in install_eggs
return self.build_and_install(setup_script, setup_base)
File
/software/z3c/formdemo/lib/python2.4/site-packages/setuptools-0.6c8-py2.4.egg/setuptools/command/easy_install.py,
line 930, in build_and_install
self.run_setup(setup_script, setup_base, args)
File
/software/z3c/formdemo/lib/python2.4/site-packages/setuptools-0.6c8-py2.4.egg/setuptools/command/easy_install.py,
line 919, in run_setup
run_setup(setup_script, args)
File
/software/z3c/formdemo/lib/python2.4/site-packages/setuptools-0.6c8-py2.4.egg/setuptools/sandbox.py,
line 26, in run_setup
DirectorySandbox(setup_dir).run(
File
/software/z3c/formdemo/lib/python2.4/site-packages/setuptools-0.6c8-py2.4.egg/setuptools/sandbox.py,
line 63, in run
return func()
File
/software/z3c/formdemo/lib/python2.4/site-packages/setuptools-0.6c8-py2.4.egg/setuptools/sandbox.py,
line 29, in lambda
{'__file__':setup_script, '__name__':'__main__'}
File setup.py, line 94, in ?
'zope.traversing',
File /opt/python24/./python/lib/python2.4/distutils/core.py, line 149, in
setup
dist.run_commands()
File /opt/python24/./python/lib/python2.4/distutils/dist.py, line 946, in
run_commands
self.run_command(cmd)
File /opt/python24/./python/lib/python2.4/distutils/dist.py, line 966, in
run_command
cmd_obj.run()
File
/software/z3c/formdemo/lib/python2.4/site-packages/setuptools-0.6c8-py2.4.egg/setuptools/command/bdist_egg.py,
line 167, in run
self.run_command(egg_info)
File /opt/python24/./python/lib/python2.4/distutils/cmd.py, line 333, in
run_command
self.distribution.run_command(command)
File /opt/python24/./python/lib/python2.4/distutils/dist.py, line 966, in
run_command
cmd_obj.run()
File
/software/z3c/formdemo/lib/python2.4/site-packages/setuptools-0.6c8-py2.4.egg/setuptools/command/egg_info.py,
line 171, in run
self.find_sources()
File
/software/z3c/formdemo/lib/python2.4/site-packages/setuptools-0.6c8-py2.4.egg/setuptools/command/egg_info.py,
line 252, in find_sources
mm.run()
File
/software/z3c/formdemo/lib/python2.4/site-packages/setuptools-0.6c8-py2.4.egg/setuptools/command/egg_info.py,
line 306, in run
self.add_defaults()
File
Re: [Distutils] Issues Tracker for Setuptools
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: http://allmydata.org/trac/setuptools Regards, Zooko ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Issues Tracker for Setuptools
-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-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B If Winter comes, can Spring be far behind..? ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
[Distutils] [issue5] setuptools uses deprecated module md5
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: asmodai priority: bug status: unread title: setuptools uses deprecated module md5 ___ Setuptools tracker [EMAIL PROTECTED] http://bugs.python.org/setuptools/issue5 ___ ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Issues Tracker for Setuptools
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 for yet-another-list if I would avoid it. Please set up a new list. I am not interested enough in setuptools (as opposed to distutils in general) to want to see all the bug reports. Paul. ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
[Distutils] [issue6] all files installed +x
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 nosetests. No final determination was received from PJE. For extensive discussion, see: http://nabble.decenturl.com/setuptools-nose-chmod- bug -- messages: 7 nosy: pfein priority: bug status: unread title: all files installed +x ___ Setuptools tracker [EMAIL PROTECTED] http://bugs.python.org/setuptools/issue6 ___ ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] [issue6] all files installed +x
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 ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] [issue6] all files installed +x
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 wrong and definitely needs to be fixed. I believe I called it broken and dangerous. Full discussion at: http://nabble.decenturl.com/setuptools-nose-chmod-bug ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
