Re: [Distutils] [buildout] "private" releases
On 4/6/2011 3:21 AM, Chris Withers wrote: > On 05/04/2011 16:33, Eric Smith wrote: >> Could you elaborate on this? How does buildout/setuptools/distribut >> search for an sdist, lacking an index file? Does it look for .tgz only, >> or other extensions as well? This would save me a ton of heartburn if I >> could get it to work. > > Point find-links at either a folder on disk, or that sample folder > served over http by Apache's normal folder serving (ie: index listings on). > > Just stick any type of dist into that folder. > > The rest "just works". > > If it doesn't, explain what you did and we'll see if we can spot what > went wrong... Finally following up on this. Yes, just using "Options +Indexes" works fine. Thanks. Eric. ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] dependencies, pip and non-PyPI-hosted packages
On Tue, Apr 26, 2011 at 7:30 PM, Tres Seaver wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 04/26/2011 12:02 PM, Ernesto Posse wrote: >> On Sat, Apr 23, 2011 at 3:12 PM, Carl Meyer wrote: >>> >>> >>> On 04/23/2011 02:00 PM, P.J. Eby wrote: At 04:54 PM 4/22/2011 -0500, Carl Meyer wrote: > No, it is calling the distribute setup. If you look at how your package > is installed, you'll find it in an egg - that's a sure sign of > setuptools/distribute. It's just that "python setup.py install" does not > handle dependencies, even with setuptools/distribute. Uh, yes it does, actually. (At least with setuptools, it does; don't know about distribute.) >>> >>> Erp. Yeah, you're right; just verified that it works fine with both >>> setuptools and distribute. Dunno where I got that idea. >>> >>> Carl >> >> >> I'm confused now. I have tried both with setuptools alone (using >> ez_setup.py instead of distribute_setup.py) and distribute, and it >> doesn't work with distribute alone for me: it doesn't install the >> dependencies and gives me those warnings about 'install_requires' not >> being recognized. >> >> Any ideas about what could be wrong? > > How are you invoking setup? Should be something like: > > from setuptools import setup > > setup(name='your.package', > ... > install_requires=['other.packaage'], > ) > The version using distribute (which doesn't get the dependencies and looks as if it was calling the distutils setup) is this: # Begin of setup.py with distribute from distribute_setup import use_setuptools use_setuptools() from setuptools import setup, find_packages setup(name="project3",..., install_requires=['project1','project2'],...,dependency_links=['http://my.host.org/repository/'],...) # End of setup.py with distribute The version that uses only setuptools and not distribute (and does pick the dependencies) is as follows: # Begin of setup.py with setuptools from ez_setup import use_setuptools use_setuptools() from setuptools import setup, find_packages setup(name="project3",..., install_requires=['project1','project2'],...,dependency_links=['http://my.host.org/repository/'],...) # End of setup.py with setuptools The only difference is using ez_setup instead of distribute_setup (the MANIFEST.in file is updated accordingly). I have tried both in "clean" enviroments, removing both setuptools and distribute. Of course, if I do use pip instead of "python setup install" it works just fine. > Tres. > - -- > === > Tres Seaver +1 540-429-0999 tsea...@palladion.com > Palladion Software "Excellence by Design" http://palladion.com > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.10 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk23VXsACgkQ+gerLs4ltQ5O6gCfd8WzYUb6+bWlGvPC/ZUsfcHu > NtIAn1pFAvWtvTV8Slap6Iopl2sT/5UD > =Hi4F > -END PGP SIGNATURE- > > ___ > Distutils-SIG maillist - Distutils-SIG@python.org > http://mail.python.org/mailman/listinfo/distutils-sig > -- Ernesto Posse Modelling and Analysis in Software Engineering School of Computing Queen's University - Kingston, Ontario, Canada ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] dependencies, pip and non-PyPI-hosted packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/26/2011 12:02 PM, Ernesto Posse wrote: > On Sat, Apr 23, 2011 at 3:12 PM, Carl Meyer wrote: >> >> >> On 04/23/2011 02:00 PM, P.J. Eby wrote: >>> At 04:54 PM 4/22/2011 -0500, Carl Meyer wrote: No, it is calling the distribute setup. If you look at how your package is installed, you'll find it in an egg - that's a sure sign of setuptools/distribute. It's just that "python setup.py install" does not handle dependencies, even with setuptools/distribute. >>> >>> Uh, yes it does, actually. (At least with setuptools, it does; don't >>> know about distribute.) >> >> Erp. Yeah, you're right; just verified that it works fine with both >> setuptools and distribute. Dunno where I got that idea. >> >> Carl > > > I'm confused now. I have tried both with setuptools alone (using > ez_setup.py instead of distribute_setup.py) and distribute, and it > doesn't work with distribute alone for me: it doesn't install the > dependencies and gives me those warnings about 'install_requires' not > being recognized. > > Any ideas about what could be wrong? How are you invoking setup? Should be something like: from setuptools import setup setup(name='your.package', ... install_requires=['other.packaage'], ) Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk23VXsACgkQ+gerLs4ltQ5O6gCfd8WzYUb6+bWlGvPC/ZUsfcHu NtIAn1pFAvWtvTV8Slap6Iopl2sT/5UD =Hi4F -END PGP SIGNATURE- ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] dependencies, pip and non-PyPI-hosted packages
On Sat, Apr 23, 2011 at 3:12 PM, Carl Meyer wrote: > > > On 04/23/2011 02:00 PM, P.J. Eby wrote: >> At 04:54 PM 4/22/2011 -0500, Carl Meyer wrote: >>> No, it is calling the distribute setup. If you look at how your package >>> is installed, you'll find it in an egg - that's a sure sign of >>> setuptools/distribute. It's just that "python setup.py install" does not >>> handle dependencies, even with setuptools/distribute. >> >> Uh, yes it does, actually. (At least with setuptools, it does; don't >> know about distribute.) > > Erp. Yeah, you're right; just verified that it works fine with both > setuptools and distribute. Dunno where I got that idea. > > Carl I'm confused now. I have tried both with setuptools alone (using ez_setup.py instead of distribute_setup.py) and distribute, and it doesn't work with distribute alone for me: it doesn't install the dependencies and gives me those warnings about 'install_requires' not being recognized. Any ideas about what could be wrong? -- Ernesto Posse Modelling and Analysis in Software Engineering School of Computing Queen's University - Kingston, Ontario, Canada ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
[Distutils] symlinks in sources
I am trying to figure out the intended behaviour of dealing with symlinks in package sources. My use case is that I have a number of package implementation web things, and they tend to have an interactive (static) prototype parts of which are reused directly in the application. The filesystem structure for those packages is one of two options: 1. Prototype is at the toplevel of the source. For example: Prototype/index.html Prototyle/style/main.css setup.py MANIFEST.in src/namespace/__init__.py src/namespace/templates/index.html src/namespace/templates/style -> ../../../Prototype/style 2. Prototype is at outside the source. For example: Prototype/index.html Prototyle/style/main.css buildout/bootstrap.py buildout/buildout.cfg buildout/src/mypackage/setup.py buildout/src/mypackage/MANIFEST.in buildout/src/mypackage/src/namespace/__init__.py buildout/src/mypackage/src/namespace/templates/index.html buildout/src/mypackage/src/namespace/templates/style -> ../../../../../../Prototype/style My goal is to be able to create an sdist for my package and upload that to pypi, and when people install that namespace/templates/style/main.css must exist. Currently this does not appear to be possible. The problems I see are: a) symlinks are skipped by distutils b) if you use a file finder plugin which traverses the symlink and reports the files they end up twice in the sdist: once for the Prototype and once inside the package. They second one is stored as a link inside the sdist, but that link is not unpacked when installing from the sdist and the files go missing. Trying to analyse things a bit I see a number of possible scenarios for symlinks: i) symlink pointing to file inside the packgage ii) symlink pointing to directory inside the packgage iii) symlink pointing to file outside the packgage, but in SCM iv) symlink pointing to directory outside the packgage, but in SCM v) symlink pointing to something outside package and not managed by SCM My expectation is that i and ii work out of the box, iii and iv should work if you have a file finder plugin for setuptools that traverses the symlink, and v to not work. Is that expectation reasonable? Wichert. ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
