Mailman 3 June 2006 - Distutils-SIG

Re: [Distutils] unrecognised swig options ?
by Phillip J. Eby June 29, 2006

June 29, 2006

At 03:49 PM 6/10/2006 +0800, Risky Martin wrote: >2006/6/7, Risky Martin <<mailto:risky.martin@gmail.com> >risky.martin(a)gmail.com>: >>I am trying to use disutils's features with 'SWIG'... but hit >>a rather strange problem. >> >>To reproduce it: >> >>setup.py >>------------------------------------------------------ >>from distutils.core import setup, Extension >> >>e = Extension("_foo", >> sources = ["foo.i", ], >> swig_opts = ["-outdir .", ]) >> >> >>setup(name="foo", >> ext_modules=[e, ]) >>------------------------------------------------------- >> >>building fails like: >> >> > python setup.py build >>running build >>running build_ext >>building '_foo' extension >>swigging foo.i to foo_wrap.c >>swig -python -outdir . -o foo_wrap.c foo.i >>swig error : Unrecognized option -outdir . >>Use 'swig -help' for available options. >>error: command 'swig' failed with exit status 1 >> >>but a copy/paste of the swig command shows that '-outdir' *is* recognised... >> > swig -python -outdir . -o foo_wrap.c foo.i >>Unable to find file 'foo.i'. Are you sure that you are running the same swig on the command line that Python is running?

1 0

Problem between bdist_msi and egg-info (Python 2.5b1)
by Paul Moore June 29, 2006

June 29, 2006

If I try to build a bdist_msi installer for a trivial module, using Python 2.5b1, I get an error. It looks like a problem with the interaction of the new (in 2.5) egg-info stuff and the bdist_msi code - but I have no further ideas. Here is the setup.py from distutils.core import setup setup( name='test', version='1.0', py_modules=['test'], ) And here is the build output: >python setup.py bdist_msi running bdist_msi running build running build_py creating build creating build\lib copying test.py -> build\lib installing to build\bdist.win32\msi running install_lib creating build\bdist.win32 creating build\bdist.win32\msi creating build\bdist.win32\msi\Lib creating build\bdist.win32\msi\Lib\site-packages copying build\lib\test.py -> build\bdist.win32\msi\Lib\site-packages running install_egg_info Writing build\bdist.win32\msi\Lib\site-packages\test-1.0-py2.5.egg-info creating dist Traceback (most recent call last): File "setup.py", line 5, in <module> py_modules=['test'], File "D:\Apps\Python25\Lib\distutils\core.py", line 151, in setup dist.run_commands() File "D:\Apps\Python25\Lib\distutils\dist.py", line 974, in run_commands self.run_command(cmd) File "D:\Apps\Python25\Lib\distutils\dist.py", line 994, in run_command cmd_obj.run() File "D:\Apps\Python25\Lib\distutils\command\bdist_msi.py", line 235, in run self.add_files() File "D:\Apps\Python25\Lib\distutils\command\bdist_msi.py", line 263, in add_files key = dir.add_file(file) File "D:\Apps\Python25\Lib\msilib\__init__.py", line 343, in add_file language, attributes, sequence)]) File "D:\Apps\Python25\Lib\msilib\__init__.py", line 115, in add_data raise MSIError("Could not insert "+repr(values)+" into "+table) _msi.MSIError: Could not insert [(None, 'site_packages', 'TEST-1~1.EGG|test-1.0-py2.5.egg-info', 186L, None, None, 512, 1)] into File I can't log a SF bug at the moment, as SF isn't accepting logins, but maybe someone could take a look and judge where the problem lies. Then when I can log a bug, I can put it in the right category :-) Thanks, Paul.

1 0

Re: [Distutils] Best practices for creating eggs?
by Phillip J. Eby June 29, 2006

June 29, 2006

At 10:37 AM 6/29/2006 +0100, Paul Moore wrote: >On 6/28/06, Phillip J. Eby <pje(a)telecommunity.com> wrote: >>I assume that most people will read the docs on the web, and that if they >>want the documentation source, they will download the "sdist" distribution >>that I always upload alongside of the eggs. > >I work offline sufficiently often that not having local documentation >is frustrating. There's no standard for local docs, which is a >nuisance, and makes for an inconsistent story between different >packages, but I'd be concerned if setuptools made it more difficult to >bundle local docs. > >An example - cx_Oracle provides a full set of HTML documentation which >the bdist_wininst installer drops in C:\Python24\cx_Oracle-doc. The >one time I tried using easy_install to convert this to an egg, the >documentation got missed out. I've never retried the experiment, >however, so things could well have changed, as this was quite a while >ago. > >And of course, eggs which get installed as zip files don't really >offer anywhere to *put* documentation which is accessible (web >browsers can't load HTML out of zip files, for example). Note that I said above that I always put the documentation in an sdist form; to obtain a package's source distribution, use: easy_install -e -b somedir arg... Where 'arg...' is some specification of a package, and 'somedir' is the parent directory of where you want the package's source to be unpacked or checked out. If you requested e.g. 'cx_Oracle', you will end up with a 'somedir/cx_oracle' directory containing the extracted source distribution. You can then decide what to do with any docs in it. A standard for how to install documentation would be great, because then you could run the docinstall command or whatever it's called on the source directory. For that matter, easy_install could be made to do it also. (Of course, this could presumably be included in eggs also, but I'm thinking of it being a separate operation from installing the eggs, just because it's increasingly common to be installing a package to satisfy some other package's dependency -- not because you actually intend to use that package directly. OTOH, relatively small packages compared to their documentation size might just want to throw it in.)

2 1

Best practices for creating eggs?
by Jim Fulton June 29, 2006

June 29, 2006

Has anyone written up any best practices for creating eggs? How do people handle documentation? Our packages tend to have documentation files included as doctests, but It's not clear how folks are expected to get to them, especially if the eggs are zip files. -- 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

4 4

How does one register a framework classifier?
by Jim Fulton June 29, 2006

June 29, 2006

How does one register a new Framework classifier? 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

3 4

README(.txt)?
by Jim Fulton June 28, 2006

June 28, 2006

If I don't have a README or README.txt file next to my setup.py file when I create an edd, I'll get the warning: warning: manifest_maker: standard file not found: should have one of README, README.txt I don't like warnings. So I create a REAME,txt file and then generate an egg and, guess what? It's not included. Bug or feature? 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 2

setup.py develop ignores --no-deps option
by Jim Fulton June 25, 2006

June 25, 2006

AFAICT, with 0.6b3, setup.py develop ignores the --no-deps option. 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

1 0

conditional external packages dependancies with setuptools
by Jorge Vargas June 24, 2006

June 24, 2006

sorry forgot to send this to the list. ---------- Forwarded message ---------- From: Jorge Vargas <jorge.vargas(a)gmail.com> Date: Jun 24, 2006 4:13 PM Subject: Re: [Distutils] conditional external packages dependancies with setuptools To: "Phillip J. Eby" <pje(a)telecommunity.com> On 6/24/06, Phillip J. Eby <pje(a)telecommunity.com> wrote: > At 01:29 PM 6/24/2006 -0400, Jorge Vargas wrote: > >On 6/24/06, Phillip J. Eby > ><<mailto:pje@telecommunity.com>pje(a)telecommunity.com > wrote: > >>At 03:04 AM 6/24/2006 -0400, Jorge Vargas wrote: > >> >but What I want to accomplish is having dependancies on some packages. > for > >> >example my project will have diferent database backends so I want to > >> >depend on pysqlite or mysql-python depending on which the user wants > as > >> >his/her backend. I'm going to have lots of diferent backends, even > some > >> >that are not databases, so this will be a crutial thing for me or I'll > end > >> >up with very big dist files per release, which will mostly be waste if > the > >> >user never uses them. > >> > > >> >is something like this possible with setuptools now? > >> > >>Yes: > >> > >><http://peak.telecommunity.com/DevCenter/setuptools#declaring-extras>http://peak.telecommunity.com/DevCenter/setuptools#declaring-extras > >> > > > >there it says that I can set them and then project depending on mine > will > >be able to add them to their install_required, but what I want is my > >project to have it optional > > > >there is a reference that they can be pass as commands to easy_install > but > >can't find the switch at > ><http://peak.telecommunity.com/DevCenter/EasyInstall#command-line-options > >http://peak.telecommunity.com/DevCenter/EasyInstall#command-line-options > > If you have an optional feature called "bar" for your package named "foo", > you would use: > > easy_install foo[bar] > > if there's also a "baz" feature and the user wants to install that too, > they can use: > > easy_install foo[bar,baz] ahh yes now I remenber TurboGears uses those. will there be a way to create defaults for this or maybe provide diferent "instalation scripts" for example <mypackage>-minimal.py equivalente of easy_install <mypackage> <mypackage>-std.py equivalente of easy_install <mypackage> [for,bar] <mypackage>-full.py equivalente of easy_install <mypackage> [for,bar,baz,bazz] >I'm looking at something like the gentoo's USE flags system. where I can > >have a script or config file that each install will use with the optional > >packages they want, and distribute that with a sane number of defaults. > > I'm not familiar with this, although it sounds like something that might > be > useful to add in future. Presumably this could be done by standardizing > names of "extras" and then having an option for easy_install (which then > would be configurable via the normal distutils config files). I'll keep > that in mind for 0.7. yes indeed is one of the most powerfull feature of emerge. the way it works on gentoo is as follows. there is a global config file (/etc/make.conf) that has all the global useflags the user has set then each package can set it's own set of useflags so when someone installs something the engine sets its global flags and then looks for package specific (package.use) and then for commandline flags, although commandline in gentoo is deprecated due to errors in stuff like package A I needs foo compile with bar support... anyway. I'll love to see something like this for setuptools this will make it easier to integrate into gentoo since one of the biggest problems right now with easy_install in gentoo is the lack of flexibility in the instalation. ohh I almost forgot a big part of emerge is build on python, so maybe even some code could be borrow.

1 0

Re: [Distutils] conditional external packages dependancies with setuptools
by Phillip J. Eby June 24, 2006

June 24, 2006

At 01:29 PM 6/24/2006 -0400, Jorge Vargas wrote: >On 6/24/06, Phillip J. Eby ><<mailto:pje@telecommunity.com>pje(a)telecommunity.com> wrote: >>At 03:04 AM 6/24/2006 -0400, Jorge Vargas wrote: >> >but What I want to accomplish is having dependancies on some packages. for >> >example my project will have diferent database backends so I want to >> >depend on pysqlite or mysql-python depending on which the user wants as >> >his/her backend. I'm going to have lots of diferent backends, even some >> >that are not databases, so this will be a crutial thing for me or I'll end >> >up with very big dist files per release, which will mostly be waste if the >> >user never uses them. >> > >> >is something like this possible with setuptools now? >> >>Yes: >> >><http://peak.telecommunity.com/DevCenter/setuptools#declaring-extras>http://peak.telecommunity.com/DevCenter/setuptools#declaring-extras >> > >there it says that I can set them and then project depending on mine will >be able to add them to their install_required, but what I want is my >project to have it optional > >there is a reference that they can be pass as commands to easy_install but >can't find the switch at ><http://peak.telecommunity.com/DevCenter/EasyInstall#command-line-options>http://peak.telecommunity.com/DevCenter/EasyInstall#command-line-options If you have an optional feature called "bar" for your package named "foo", you would use: easy_install foo[bar] if there's also a "baz" feature and the user wants to install that too, they can use: easy_install foo[bar,baz] >I'm looking at something like the gentoo's USE flags system. where I can >have a script or config file that each install will use with the optional >packages they want, and distribute that with a sane number of defaults. I'm not familiar with this, although it sounds like something that might be useful to add in future. Presumably this could be done by standardizing names of "extras" and then having an option for easy_install (which then would be configurable via the normal distutils config files). I'll keep that in mind for 0.7.

1 0

Re: [Distutils] conditional external packages dependancies with setuptools
by Phillip J. Eby June 24, 2006

June 24, 2006

At 03:04 AM 6/24/2006 -0400, Jorge Vargas wrote: >but What I want to accomplish is having dependancies on some packages. for >example my project will have diferent database backends so I want to >depend on pysqlite or mysql-python depending on which the user wants as >his/her backend. I'm going to have lots of diferent backends, even some >that are not databases, so this will be a crutial thing for me or I'll end >up with very big dist files per release, which will mostly be waste if the >user never uses them. > >is something like this possible with setuptools now? Yes: http://peak.telecommunity.com/DevCenter/setuptools#declaring-extras

1 0