Mailman 3 January 2007 - Distutils-SIG

Re: [Distutils] Skipping namespace file?
by Phillip J. Eby Jan. 6, 2007

Jan. 6, 2007

At 03:46 PM 1/6/2007 -0500, Kurt Schwehr wrote: >Sounds good, but I still am confused as to why there should not be a >site-packages/dap/__init__.py in the installed lib area. For this package >there isn't too much in there, but some packages include things like >version numbers and defaults in their __init__.py. Yes, but then they shouldn't declare them (implicitly or explicitly) as namespace packages. A namespace package, by definition, is one whose sole purpose is to provide a namespace for modules and subpackages. It cannot provide any contents of its own. > For dap, we would be leaving out the overview documentation for import > dap;help(dap). If the case really is that there should not be a > dap/__init__.py, where do I tell the author of the package to move that > documentation such that help(dap) will still provide as much info? There isn't any such place, I'm afraid. The alternative would be to use some other package as a base for plugins and responses, e.g. dap_ext.plugins and dap_ext.responses, so that 'dap' would not be a namespace package itself.

1 0

Re: [Distutils] Skipping namespace file?
by Phillip J. Eby Jan. 6, 2007

Jan. 6, 2007

At 09:05 AM 1/5/2007 -0500, Kurt Schwehr wrote: >Here is what the pth looks like. Is there something wrong with it then? > >cat /sw/lib/python2.5/site-packages/dap-2.2.5.7-py2.5-nspkg.pth >import sys,new,os; p = os.path.join(sys._getframe(1).f_locals['sitedir'], >*('dap', 'plugins')); ie = os.path.exists(os.path.join (p,'__init__.py')); >m = not ie and >sys.modules.setdefault('dap.plugins',new.module('dap.plugins')); mp = (m >or []) and m.__dict__.setdefault('__path__',[]); (p not in mp) and mp.append(p) >import sys,new,os; p = os.path.join(sys._getframe(1).f_locals['sitedir'], >*('dap', 'responses')); ie = >os.path.exists(os.path.join(p,'__init__.py')); m = not ie and >sys.modules.setdefault(' dap.responses',new.module('dap.responses')); mp = >(m or []) and m.__dict__.setdefault('__path__',[]); (p not in mp) and >mp.append(p) > >If I read that right, it is not letting python know about the dap module, >so that I can't do something like "import dap.client". Does this mean >that the setup.py is not configured correctly to include a "dap"? Yes, you're right, that is exactly the problem. There are two possible fixes: 1. add 'dap' to the namespace_packages setting in the setup.py 2. change setuptools to figure out that this is needed Since setuptools already knows that it shouldn't include the __init__ for dap, it can reasonably be considered a setuptools bug that it doesnt' generate the .pth correctly for that case, so I will fix that. In the meantime, as a workaround, adding 'dap' to the namespace_packages setting will allow you to proceed. Thanks for your patience and help in identifying the actual bug.

2 1

Adding a setuptool command that runs when setup.py build is invoked
by Scott Robertson Jan. 6, 2007

Jan. 6, 2007

I'm trying to create a package that provides a setuptool command that will compile idl files when you run python setup.py build or python setup.pyinstall. I've figured out how to add an additional command (build_omniidl) which I can run with: python setup.py build_omniidl But I'm not sure how to wire it up so that python setup.py build automatically invokes build_omniidl for me. Basically I want build_omniidl to act just like build_python. Is this even possible with setuptools? If so anyone know where I can see an example?

1 0

Re: [Distutils] Skipping namespace file?
by Phillip J. Eby Jan. 5, 2007

Jan. 5, 2007

I've now fixed the bug below in both the 0.6 branch and the development trunk. You can get them by easy_installing either 'setuptools==dev06' or 'setuptools==dev', respectively. At 11:43 AM 1/5/2007 -0500, Phillip J. Eby wrote: >At 09:05 AM 1/5/2007 -0500, Kurt Schwehr wrote: > >If I read that right, it is not letting python know about the dap module, > >so that I can't do something like "import dap.client". Does this mean > >that the setup.py is not configured correctly to include a "dap"? > >Yes, you're right, that is exactly the problem. There are two possible fixes: > >1. add 'dap' to the namespace_packages setting in the setup.py > >2. change setuptools to figure out that this is needed > >Since setuptools already knows that it shouldn't include the __init__ for >dap, it can reasonably be considered a setuptools bug that it doesnt' >generate the .pth correctly for that case, so I will fix that. In the >meantime, as a workaround, adding 'dap' to the namespace_packages setting >will allow you to proceed. > >Thanks for your patience and help in identifying the actual bug.

1 0

Re: [Distutils] Skipping namespace file?
by Phillip J. Eby Jan. 5, 2007

Jan. 5, 2007

At 10:47 AM 1/3/2007 -0500, Kurt Schwehr wrote: >Hi All, > >I am working on packaging pydap and am getting some strange behavior. > >Here is the install phase... > >/sw/bin/python2.4 setup.py install >--root=/sw/src/fink.build/root-dap-py24-2.2.5.7-1 >--single-version-externally-managed > > >And when it gets to the __init__.py file for dap, it skips it. This >causes the package to not work. It should also be installing a .pth file that makes it work, but if your final installation destination is not a 'site' directory (e.g. Python's site-packages directory), this will not work. > Anyone have an idea why it is doing this? Because system packaging tools like RPM et al do not like it when multiple packages install the same file. dap.plugins and dap.responses are "namespace packages", which means that other projects can install modules in them. Those modules mustn't install an __init__.py, as it would overwrite the one supplied by pydap. The setuptools solution to this problem is to never install an __init__.py at all for such packages, when used with a packaging tool (which is implied by the use of --root). Instead, setuptools generates a uniquely-named .pth file for each project, that sets up the namespace package at runtime. Look for a .pth file being placed in your /sw/src/fink.build/root-dap-py24-2.2.5.7-1/sw/lib/python2.4/site-packages/ directory. The problem is that if you then install the package somewhere other than /sw/lib/python2.4/site-packages, or use the -S option to Python at runtime, it may not work. >This install proceedure works well with other packages in mac osx/fink. I >also see the behavior without the --single-version-externally-managed flag. That's because --root implies --single-version-externally-managed.

2 1

tests_require and test_suite in egg-info
by Jim Fulton Jan. 5, 2007

Jan. 5, 2007

It appears that the values of the tests_require and test_suite keyword arguments isn't captured in egg-info. Am I missing something? Why would this information be omitted? I would like to use it when generating test runners in zc.buildout. Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org

2 4

[setuptools] egg_info and install_requires
by Ronald Oussoren Jan. 5, 2007

Jan. 5, 2007

Hi, I have a setup.py that has some projects in the install_requires list that setuptools cannot find yet (I haven't build the eggs yet) and noticed something odd. When there is not yet an .egg-info directory for my project everything is fine, I can run distutils commands (except install of course). However, when the .egg-info directory is present all distutils commands fail, including the egg_info command, because I'm refering to a non-existing distribution. Is this supposed to happen? Ronald

2 2

Re: [Distutils] setuptools patch for egg_info.get_svn_revision; max() doesn't like an empty list
by Phillip J. Eby Jan. 5, 2007

Jan. 5, 2007

At 10:22 PM 1/4/2007 -0600, Kumar McMillan wrote: >hi folks. >I looked high and low for an official spot to submit setuptools >patches but just found this mailing list. Please accept my apologies >in advance if this is inconvenient. Thanks; but a fix for this is already in the SVN trunk; you can get it with: easy_install setuptools==dev06

1 0

setuptools patch for egg_info.get_svn_revision; max() doesn't like an empty list
by Kumar McMillan Jan. 5, 2007

Jan. 5, 2007

hi folks. I looked high and low for an official spot to submit setuptools patches but just found this mailing list. Please accept my apologies in advance if this is inconvenient. I found that when running setup.py commands on an svn checkout while having just added a directory, but not committed it yet, I would get "ValueError: max() arg is an empty sequence" from around line 227 of egg_info.py. This seems easily fixable by checking the length of all_revs before handing it to max() and the patch attached solves the problem I was having. After applying the patch to the source, `python setup.py test` ran ok. thanks, Kumar

1 0

Skipping namespace file?
by Kurt Schwehr Jan. 3, 2007

Jan. 3, 2007

Hi All, I am working on packaging pydap and am getting some strange behavior. Here is the install phase... /sw/bin/python2.4 setup.py install --root=/sw/src/fink.build/root- dap-py24-2.2.5.7-1 --single-version-externally-managed And when it gets to the __init__.py file for dap, it skips it. This causes the package to not work. Anyone have an idea why it is doing this? copying dap/wsgi/paster_templates/template/index.tmpl -> build/lib/dap/wsgi/paster_templates/template running install_lib Skipping installation of /sw/src/fink.build/root-dap-py24-2.2.5.7-1/sw/lib/python2.4/site-packages/dap/__init__.py (namespace package) copying dap/client.py -> /sw/src/fink.build/root-dap-py24-2.2.5.7-1 /sw/lib/python2.4/site-packages/dap I am using this version of pydap: http://cheeseshop.python.org/packages/source/d/dap/dap-2.2.5.7.tar.gz This install proceedure works well with other packages in mac osx/fink. I also see the behavior without the --single-version-externally-managed flag. Anyone have a suggestion as to what's going on? Thanks!! -kurt http://schwehr.org/

1 0