Mailman 3 August 2008 - Distutils-SIG

Distutils / Setuptools on Windows: Can we use local or UNC filesystems as an argument to --find-links
by Fadhley Salim Aug. 12, 2008

Aug. 12, 2008

A project I'm working on requires a Python egg to be deployed to a remote location which (because of a security configuration outside my control) denies users access to the web-servers we use to load eggs from the office I work. I've determined that the security at this location allows users access to Windows networked file-systems. It has been proposed that rather than creating a web-repository for python eggs we store these on a local file-server. But from what I can tell the easy_install utility can ONLY load it's eggs from web-servers. Has anybody had any luck using the --find_options argument to easy_install with a local folder (e.g. on a Windows C: Drive) or a network folder, for example easy_install --find-links="http://server/egs" myegg==1.0.1 ( that sort of thing works fine ) but what about: easy_install --find-links="c:\myeggs\" myegg==1.0.1 or even: easy_install --find-links="file:///c:/myeggs" myegg==1.01 and with a UNC path: easy_install --find-links="file://///myserver/webapps/eggs/" myegg==1.01 If (as I suspect) easy_install cannot support anything other than a direct-http set-up is there a way for me to simply modify the code for easy_install to do this? Furthermore, since we like to be up to date I dont want to run a permanently forked version of setuptools - can we submit any changes back to the project so we do not have to be permanently forked? Thanks This email does not create a legal relationship between any member of the Crédit Agricole group and the recipient or constitute investment advice. The content of this email should not be copied or disclosed (in whole or part) to any other person. It may contain information which is confidential, privileged or otherwise protected from disclosure. If you are not the intended recipient, you should notify us and delete it from your system. Emails may be monitored, are not secure and may be amended, destroyed or contain viruses and in communicating with us such conditions are accepted. Any content which does not relate to business matters is not endorsed by us. Calyon is authorised by the Commission Bancaire in France and regulated by the Financial Services Authority for the conduct of business in the United Kingdom. Calyon is incorporated in France with limited liability and registered in England & Wales. Registration number: FC008194. Registered office: Broadwalk House, 5 Appold Street, London, EC2A 2DA.

1 0

specify available build commands
by chris Aug. 12, 2008

Aug. 12, 2008

Is there a way in distutils / setuptools to list the available build commands via porperty or function? Specifically, I want to be able to add a configuration and build some classes only if one of these commands is specified. python setup.py build <----- confuguration added python setup.py sdist bdist_egg <----- confuguration added python setup.py sdist <----- confuguration not added Maybe there's a better way to do it. -Chris

2 1

[issue32] Make setuptools hanlde multiple index locations (index url)
by Tarek Ziadé Aug. 12, 2008

Aug. 12, 2008

New submission from Tarek Ziadé <ziade.tarek(a)gmail.com>: PyPI mirrors and alternative packages servers are starting to appear. To be able to use them efficiently, setuptools should be able to handle a list of index url instead of a single one. That would involve playing with several instance of PackageIndex but would allow retrieving packages from several sources, whether they are mirrors or alternative package servers. ---------- messages: 80 nosy: tarek priority: feature status: unread title: Make setuptools hanlde multiple index locations (index url) _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue32> _______________________________________________

1 0

Setuptools reindenting reST documentation?
by Andreas Jung Aug. 12, 2008

Aug. 12, 2008

Hi there, I have a reST documentation containing something like that blablabla:: foo foo foo foo foo foo used as long_description. After building the egg the PKG-INFO file contains the text with the same indentation level. I came across this issue because rst2html.py did not complain before building the egg but a later conversion of the reST document taken from the PKG-INFO produced serveral errors. Why is setuptools doing that? Andreas

1 0

Re: [Distutils] Enthought-dev Digest, Vol 48, Issue 49
by Stanley A. Klein Aug. 11, 2008

Aug. 11, 2008

Dave - I wasn't using the release alias. From what you say, I suppose I should. I think the Enable project might be somewhat different from the others because it uses both distutils and setuptools. I will send you off line a program I used that fixes up the setup.cfg. Stan Klein On Mon, August 11, 2008 2:16 pm, enthought-dev-request(a)mail.enthought.com > Message: 5 > Date: Mon, 11 Aug 2008 12:51:33 -0500 > From: Dave Peterson <dpeterson(a)enthought.com> > Subject: Re: [Enthought-dev] Strange naming problem trying to build > Enable rpm > To: enthought-dev(a)mail.enthought.com > Cc: distutils-sig(a)python.org > Message-ID: <48A07C25.3010904(a)enthought.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Stanley A. Klein wrote: >> I was able to build rpms for Traits, Envisage, and related packages >> (e.g., >> TraitsGUI) for Fedora 7. However, when I tried to package Enable I ran >> into the following problem: The tar.gz gets built as >> Enable-3.0.0.dev-r21092.tar.gz, but when the rpm packager gets called it >> looks for Enable-3.0.0.tar.gz, doesn't find it, and errors out. I've >> copied a relevant part of the output below. >> > > I'm not sure what's happening here since the setup.cfg's for the ETS > projects should all be pretty close to the same on this issue. Are you > doing a "setup.py release bdist_rpm"? i.e. using the release alias? If > not, that's the source of the problem. > > BTW: Are you checking in your changes to setup.cfg's? If you don't have > privileges, I can make these changes so just send me a patch, set of > modified setup.cfgs, or instructions on what to do to reproduce your > changes. > > -- Dave >

2 1

Re: [Distutils] [Enthought-dev] Strange naming problem trying to build Enable rpm
by Stanley A. Klein Aug. 11, 2008

Aug. 11, 2008

[Oops. Re-sent to fix the subject line] Dave - I wasn't using the release alias. From what you say, I suppose I should. I think the Enable project might be somewhat different from the others because it uses both distutils and setuptools. I will send you off line a program I used that fixes up the setup.cfg. Stan Klein On Mon, August 11, 2008 2:16 pm, enthought-dev-request(a)mail.enthought.com > Message: 5 > Date: Mon, 11 Aug 2008 12:51:33 -0500 > From: Dave Peterson <dpeterson(a)enthought.com> > Subject: Re: [Enthought-dev] Strange naming problem trying to build > Enable rpm > To: enthought-dev(a)mail.enthought.com > Cc: distutils-sig(a)python.org > Message-ID: <48A07C25.3010904(a)enthought.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Stanley A. Klein wrote: >> I was able to build rpms for Traits, Envisage, and related packages (e.g., >> TraitsGUI) for Fedora 7. However, when I tried to package Enable I ran into the following problem: The tar.gz gets built as >> Enable-3.0.0.dev-r21092.tar.gz, but when the rpm packager gets called it looks for Enable-3.0.0.tar.gz, doesn't find it, and errors out. I've copied a relevant part of the output below. >> > > I'm not sure what's happening here since the setup.cfg's for the ETS projects should all be pretty close to the same on this issue. Are you doing a "setup.py release bdist_rpm"? i.e. using the release alias? If not, that's the source of the problem. > > BTW: Are you checking in your changes to setup.cfg's? If you don't have privileges, I can make these changes so just send me a patch, set of modified setup.cfgs, or instructions on what to do to reproduce your changes. > > -- Dave > -- Stanley A. Klein, D.Sc. Managing Principal Open Secure Energy Control Systems, LLC 8070 Georgia Avenue Silver Spring, MD 20910 301-565-4025

1 0

Best way to mirror Pypi
by Sebastien Douche Aug. 11, 2008

Aug. 11, 2008

Hi there :), We use intensively Setuptools and buildout and we are looking to increase downloading and checking speeds. What are elegant solutions ? The best way is to mirror also eggs (like a mirror debian for ex.), but it's maybe to heavy for pypi machine. Thx. -- Seb

2 1

Strange naming problem trying to build Enable rpm
by Stanley A. Klein Aug. 11, 2008

Aug. 11, 2008

I was able to build rpms for Traits, Envisage, and related packages (e.g., TraitsGUI) for Fedora 7. However, when I tried to package Enable I ran into the following problem: The tar.gz gets built as Enable-3.0.0.dev-r21092.tar.gz, but when the rpm packager gets called it looks for Enable-3.0.0.tar.gz, doesn't find it, and errors out. I've copied a relevant part of the output below. I modified the setup.cfg file for bdist_rpm (similarly to what I did for the other packages I built) and have copied it below. I don't know where the tar.gz name is set or where the name being looked for by rpm is set. I also don't know if this is an issue with the Enable setup files or with distutils/setuptools, so I'm including both lists. How do I get the proper names set? Stan Klein --------------------------------------------------------------------------- Packaging error output: copying dist/Enable-3.0.0.dev-r21092.tar.gz -> build/bdist.linux-i686/rpm/SOURCES building RPMs rpmbuild -ba --define _topdir /home/stan/svn/ets/ETS_3.0.0/Enable_3.0.0/build/bdist.linux-i686/rpm --clean build/bdist.linux-i686/rpm/SPECS/Enable.spec error: File /home/stan/svn/ets/ETS_3.0.0/Enable_3.0.0/build/bdist.linux-i686/rpm/SOURCES/Enable-3.0.0.tar.gz: No such file or directory error: command 'rpmbuild' failed with exit status 1 --------------------------------------------------------------------------- setup.cfg: [egg_info] tag_build = .dev tag_svn_revision = 1 [aliases] release = egg_info -RDb '' [nosetests] verbosity = 0 with-doctest = 1 detailed-errors = 1 with-coverage = 1 tests = enthought/enable/tests,enthought/enable2/tests,enthought/kiva/tests,enthought/kiva/agg/tests # # The following directories are included in the tests option above, when # the line starts with '# test '. To make changes in the tests option above # run the script update_setup_cfg.py. # # test enthought/enable/tests # test enthought/enable2/tests # test enthought/kiva/tests # test enthought/kiva/agg/tests # # Note: # The package enthought.enable2 is a proxy to enthought.enable and # the tests in 'enthought/enable2/tests' are testing this proxy. [install] optimize = 1 [bdist_rpm] doc_files = docs/ examples/ README.txt LICENSE.txt

2 1

patch: document "Framework :: Setuptools Plugin" and conventions for revision control plugins
by zooko Aug. 11, 2008

Aug. 11, 2008

Folks: Part of this patch documents the existence of the "Framework :: Setuptools Plugin" classifier and says when to use it. Another part documents the naming conventions which the developers of the various revision control plugins agreed to. Regards, Zooko P.S. Note that the git and hg revision control plugins didn't yet go through a renaming to conform to the agreed convention. I did for the setuptools_darcs plugin that I maintain -- you can see the leftover evidence of it here: http://pypi.python.org/pypi/setuptools_darcs_plugin I'm Cc:'ing the maintainers of the setuptools-git and setuptools-hg plugins to remind them of the existence of this convention in case they want to switch. diff -rN -u old-dw/setuptools.txt new-dw/setuptools.txt --- old-dw/setuptools.txt 2008-08-11 11:38:07.000000000 -0600 +++ new-dw/setuptools.txt 2008-08-11 11:38:07.000000000 -0600 @@ -2384,6 +2384,16 @@ how setuptools' own commands are installed: the setuptools project's setup script defines entry points for them! +If your command would be useful to other Python developers, then consider +uploading it to the `Python Package Index`_. If you do, please include the +Trove Classifier "Framework :: Setuptools Plugin" in the classifiers so that +your command will appear in the list of `packages which are setuptools +plugins`_. + +.. _Python Package Index: http://pypi.python.org/pypi +.. _packages which are setuptools plugins: http://pypi.python.org/ pypi?:action=browse&c=524 + + Adding ``setup()`` Arguments ---------------------------- @@ -2546,6 +2556,17 @@ control system itself. It *may*, however, use ``distutils.log.warn()`` to inform the user of the missing program(s). +Please model your naming conventions and documentation after the other +setuptools revision control plugins: `setuptools_bzr`_, `setuptools_mtn`_,' +`setuptools_darcs`_. Please include the Trove Classifier "Framework :: +Setuptools Plugin" in the classifiers so that your command will appear in the +list of `packages which are setuptools plugins`_. + +.. _setuptools_bzr: http://pypi.python.org/pypi/setuptools_bzr +.. _setuptools_mtn: http://pypi.python.org/pypi/setuptools_mtn +.. _setuptools_darcs: http://pypi.python.org/pypi/setuptools_darcs +.. _packages which are setuptools plugins: http://pypi.python.org/ pypi?:action=browse&c=524 + Subclassing ``Command`` -----------------------

1 0

How to create deb package
by Lumír Jasiok Aug. 10, 2008

Aug. 10, 2008

Hi, I need to create .deb package from source package. I am using distutils. Is there some working bdist_deb extension? What is best practices at this case? Any useful comments will be appreciate. Best Regards Lumir -- Lumír Jasiok VSB-TU Ostrava - Computer centre Tel: +420 59 732 3189 E-mail: lumir.jasiok(a)vsb.cz http://www.vsb.cz

4 3