Mailman 3 January 2010 - Distutils-SIG

Building extension on FreeBSD with Py_ENABLE_SHARED
by Nicholas Bastin 09 Jan '10

09 Jan '10

(This comes from trying to build python with --enable-shared, but I think the problem is not in the Python build process, but rather in distutils itself) When building python standard extensions as part of the build process from ./configure --enable-shared in 2.7 trunk on freebsd5, all the modules fail because they can't find libpython2.7.so: building '_json' extension gcc -pthread -fPIC -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I. -I./Include -I/usr/local/include -IInclude -I/u1/Python/Python-2.7a1 -c /u1/Python/Python-2.7a1/Modules/_json.c -o build/temp.freebsd-5.3-RELEASE-i386-2.7/u1/Python/Python-2.7a1/Modules/_json.o gcc -shared build/temp.freebsd-5.3-RELEASE-i386-2.7/u1/Python/Python-2.7a1/Modules/_json.o -L/usr/local/lib -lpython2.7 -o build/lib.freebsd-5.3-RELEASE-i386-2.7/_json.so /usr/bin/ld: cannot find -lpython2.7 This is because libpython2.7.so is in '.' (pre-install), and -L. isn't on the compile command. This problem doesn't happen on linux or solaris, but it turns out that's because it's special-cased in distutils.command.build_ext.finalize_options:278: # for extensions under Linux or Solaris with a shared Python library, # Python's library directory must be appended to library_dirs sysconfig.get_config_var('Py_ENABLE_SHARED') if ((sys.platform.startswith('linux') or sys.platform.startswith('gnu') or sys.platform.startswith('sunos')) and sysconfig.get_config_var('Py_ENABLE_SHARED')): if sys.executable.startswith(os.path.join(sys.exec_prefix, "bin")): # building third party extensions self.library_dirs.append(sysconfig.get_config_var('LIBDIR')) else: # building python standard extensions self.library_dirs.append('.') Adding freebsd to the list of platforms in question solves my particular problem, although I don't know enough about distutils to know if this would cause some other problem. Is there any particular reason we should not add '.' to the list of library_dirs on freebsd? -- Nick

3 4

zc.buildout generated console scripts with sys.exit
by Olaf Conradi 09 Jan '10

09 Jan '10

Hello, I wanted use zc.buildout for a program that I wrote, but noticed that the generated console script does not call sys.exit, unlike setuptools. My main function uses a structure as explained by Guido in http://www.artima.com/weblogs/viewpost.jsp?thread=4829 def main(argv=None): if argv is None: argv = sys.argv # ... return 0 if __name__ == "__main__": sys.exit(main()) Can this be supported? I noticed a patch is attached to https://bugs.launchpad.net/zc.buildout/+bug/164629 In short, my buildout looks like this: [py] recipe = zc.recipe.egg eggs = myprogram Thanks, -Olaf

2 1

zc.buildout generated console scripts with sys.exit
by Olaf Conradi 09 Jan '10

09 Jan '10

Hello, I wanted use zc.buildout for a program that I wrote, but noticed that the generated console script does not call sys.exit, unlike setuptools. My main function uses a structure as explained by Guido in http://www.artima.com/weblogs/viewpost.jsp?thread=4829 def main(argv=None): if argv is None: argv = sys.argv # ... return 0 if __name__ == "__main__": sys.exit(main()) Can this be supported? I noticed a patch is attached to https://bugs.launchpad.net/zc.buildout/+bug/164629 In short, my buildout looks like this: [py] recipe = zc.recipe.egg eggs = myprogram Thanks, -Olaf

1 0

[RFC] Python 2.7 Distutils extra features
by Tarek Ziadé 07 Jan '10

07 Jan '10

Hello, Besides the PEP-related features, I would like to add some tiny features in Distutils for Python 2.7 before the alpha stage is over : - a test command, that just uses the new unittest discovery to run unittest-compatible tests. - a new option for sdist called 'extra_files', that will allow to list extra files to be included in the distribution. these files will not be installed by 'install', just be part of the distribution. Any comments ? Regards Tarek -- Tarek Ziadé | http://ziade.org

4 7

Buildout. Can't start interpreter with -u option.
by Максим Lacrima 07 Jan '10

07 Jan '10

Hello! Suppose I have following buildout.cfg: [buildout] parts = python [python] recipe = zc.recipe.egg interpreter = python eggs = mypackage After running bin/buildout I have python interpreter in bin folder. My question is why I can't start the python interpreter with -u option, i.e. 'bin/python -u'. It fails with the following traceback: Traceback (most recent call last): File "/home/maxim/projects/ unikeeper/bin/python", line 11, in <module> _options, _args = __import__("getopt").getopt(sys.argv[1:], 'ic:m:') File "/usr/lib/python2.6/getopt.py", line 91, in getopt opts, args = do_shorts(opts, args[0][1:], shortopts, args[1:]) File "/usr/lib/python2.6/getopt.py", line 191, in do_shorts if short_has_arg(opt, shortopts): File "/usr/lib/python2.6/getopt.py", line 207, in short_has_arg raise GetoptError('option -%s not recognized' % opt, opt) getopt.GetoptError: option -u not recognized Is it a bug?

2 1

packaging terminology confusion
by Brad Allen 07 Jan '10

07 Jan '10

This quote is taken from the distutils thread "current preferred way to specify dependencies? future?", On Wed, Jan 6, 2010 at 10:55 AM, Tarek Ziadé <ziade.tarek(a)gmail.com> wrote: > On Wed, Jan 6, 2010 at 3:35 PM, John Gabriele <jmg3000(a)gmail.com> wrote: >> I'm a bit confused myself... PEP-345 says it "describes a mechanism >> for adding metadata to Python packages", but I think they really mean >> "distributions" (the things available at the PyPI). > > Yes you are right, that was a mistake. I've just fixed it. Sorry, but I'm baffled. Are we really now using the word 'distribution' for those 'things available at the PyPI'? The text inside PEP-345 uses the word 'distutils project' a lot as the name for this concept. It's very common to see the word 'package' used to refer to these 'distutils projects'; but in the Python documentation we also use the word 'package' to refer to any directory having an __init__.py. Can the word 'package' be used for both concepts? Maybe a qualifier would help, like module-package and setup-package. Normally the word 'distribution' is reserved for what lands in the 'dist' directory, such as a tarball or an egg...right?

5 8

Fwd: [RFC] Python 2.7 Distutils extra features
by Tarek Ziadé 06 Jan '10

06 Jan '10

oops, forgot to reply-all ---------- Forwarded message ---------- From: Tarek Ziadé <ziade.tarek(a)gmail.com> Date: Wed, Jan 6, 2010 at 8:04 PM Subject: Re: [Distutils] [RFC] Python 2.7 Distutils extra features To: exarkun(a)twistedmatrix.com 2010/1/6 <exarkun(a)twistedmatrix.com>: > On 05:30 pm, ziade.tarek(a)gmail.com wrote: >> >> On Wed, Jan 6, 2010 at 6:13 PM, Tarek Ziadé <ziade.tarek(a)gmail.com> wrote: >>> >>> Hello, >>> >>> Besides the PEP-related features, I would like to add some tiny >>> features in Distutils for Python 2.7 before the alpha stage is over : >>> >>> - a test command, that just uses the new unittest discovery to run >>> unittest-compatible tests. >>> >>> - a new option for sdist called 'extra_files', that will allow to list >>> extra files to be included in the distribution. these >>> files will not be installed by 'install', just be part of the >>> distribution. >> >> Ooops forgot the third one, (which might lead to further discussions): >> >> - a very basic pre/post commit hook for the install command. > > Being able to run some code after install is done would certainly be useful. > A couple things I wonder about... > > Can the packages that were just installed be imported in the post hook? I guess so. > > What kind of interaction would this have with the bdist installers? It'd be > a shame of things like bdist_rpm suffered when packages took advantage of > these hooks. These hooks will be deactivated when any bdist_* command runs install to create the binary tree. Now for bdist_rpm own hooks, I guess the best way would be to make install consumes the same two options than bdist_rpm (pre-install, post-install) so a project will be able to define a hook that is used by RPM or python setup.py install > Jean-Paul > -- Tarek Ziadé | http://ziade.org -- Tarek Ziadé | http://ziade.org

1 0

test coverage for setuptools
by anatoly techtonik 05 Jan '10

05 Jan '10

Hello, Where can I see test coverage results for setuptools package? I've got two tracebacks in last week after upgrading and that seems to be too much. I'd like to see if there are any tests for failing piece to see why they might fail before digging further. Bye! -- anatoly t.

3 5

Wrong Filename Extension
by Richard Plana 04 Jan '10

04 Jan '10

Hi, While trying to build a python project cx_Freeze-4.1.1 in this case) on Linux, I came up against the following problem:When building one of the packages (cx_Freeze.util) which is a C native extension package, the setup.py script ends up building a file with the name “util” instead of the expected “util.so” under the cx_Freeze/ subdirectory. Any ideas what the problem is? I’m building this on a Fedora 12 x86_64 box which uses python-2.6.2-2.fc12.x86_64. Note: Manually renaming the file from “util” to “util.so” ends up with a working system, but I’m guessing that’s not the ideal scenario. -- Richard Plana

1 0

[issue101] Traceback when installing readline
by techtonik 03 Jan '10

03 Jan '10

New submission from techtonik <techtonik(a)gmail.com>: Python 2.6 on Vista C:\Python26\Scripts>python -m easy_install readline Searching for readline Reading http://pypi.python.org/simple/readline/ Reading http://www.python.org/ Best match: readline 2.6.4 Downloading http://pypi.python.org/packages/source/r/readline/readline-2.6.4.tar.gz#md5… Processing readline-2.6.4.tar.gz Running readline-2.6.4\setup.py -q bdist_egg --dist-dir c:\users\myuser\appdata\local\temp\easy_install-yxalev\readline-2.6.4\egg-dist-tmp-7rtcal The system cannot find the path specified. Traceback (most recent call last): File "C:\Python26\lib\runpy.py", line 122, in _run_module_as_main "__main__", fname, loader, pkg_name) File "C:\Python26\lib\runpy.py", line 34, in _run_code exec code in run_globals File "C:\Python26\lib\site-packages\setuptools-0.6c11-py2.6.egg\easy_install.py", line 5, in <module> File "C:\Python26\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\easy_install.py", line 1712, in main File "C:\Python26\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\easy_install.py", line 1700, in with_ei_usage File "C:\Python26\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\easy_install.py", line 1716, in <lambda> File "C:\Python26\lib\distutils\core.py", line 152, in setup dist.run_commands() File "C:\Python26\lib\distutils\dist.py", line 975, in run_commands self.run_command(cmd) File "C:\Python26\lib\distutils\dist.py", line 995, in run_command cmd_obj.run() File "C:\Python26\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\easy_install.py", line 211, in run File "C:\Python26\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\easy_install.py", line 446, in easy_install File "C:\Python26\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\easy_install.py", line 476, in install_item File "C:\Python26\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\easy_install.py", line 655, in install_eggs File "C:\Python26\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\easy_install.py", line 930, in build_and_install File "C:\Python26\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\easy_install.py", line 919, in run_setup File "C:\Python26\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\sandbox.py", line 62, in run_setup File "C:\Python26\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\sandbox.py", line 105, in run File "C:\Python26\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\sandbox.py", line 64, in <lambda> File "setup.py", line 93, in <module> AttributeError: 'module' object has no attribute 'symlink' ---------- messages: 484 nosy: techtonik priority: bug status: unread title: Traceback when installing readline _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue101> _______________________________________________

1 0