Hi, I realized that extra-path is not always honored in buildout. I have a Django application that uses django-recipe with extra-path. I also want a pure ipython program that share the same sys.path. but if I write: [ipython] recipe = zc.recipe.egg eggs = ${buildout:eggs} extra-paths = ${buildout:directory}/apps I get a script that doesn't have the extra-path. I explicitly have to add: interpreter = ipython-dj is this the desired behaviour? sandro -- Sandro Dentella *:-) http://trepalchi.it Il portale degli artisti http://www.reteisi.org Soluzioni libere per le scuole http://sqlkit.argolinux.org SQLkit home page - PyGTK/python/sqlalchemy
On Tue, Nov 28, 2017 at 4:33 AM, Alessandro Dentella <sandro@e-den.it> wrote:
Hi,
I realized that extra-path is not always honored in buildout. I have a Django application that uses django-recipe with extra-path.
I also want a pure ipython program that share the same sys.path. but if I write:
[ipython] recipe = zc.recipe.egg eggs = ${buildout:eggs} extra-paths = ${buildout:directory}/apps
I get a script that doesn't have the extra-path. I explicitly have to add:
interpreter = ipython-dj
is this the desired behaviour?
The extra-paths egg recipe option should work, regardless of whether the interpreter option is used. Please create an issue: https://github.com/buildout/buildout/issues/new and include a full configuration file that demonstrates the problem so we can try to reproduce. Jim -- Jim Fulton http://jimfulton.info
participants (2)
-
Alessandro Dentella -
Jim Fulton