If you're using

[buildout]
develop = .

then buildout will run python setup.py develop for you

On Thursday, April 23, 2015 at 1:18:36 PM UTC+2, Jo G wrote:
>
> I'm not sure if this is the best place to ask this question so please 
> point me elsewhere if it isn't.
>
> I am using a buildout script to create an environment which uses the 
> pyramid framework and substanced. I then create a pyramid project using the 
> substanced scaffold. This project needs to import some code I have written 
> and installed using buildout and mr developer as a develop-egg.
>
> I can start my application using 
>
>     $VENV/bin/pserve development.ini --reload
>
> This runs my application but it is not working how I would expect so I 
> want to debug it.
>
> To do this I first type the command
>
>      $VENV/bin/python setup.py develop
>
> before I start the application . 
>
> Unfortunately running setup.py overwrites all my scripts in the bin folder 
> and downloads eggs from pypi for all the dependencies of my project (eg 
> pyramid and substanced) into the site-packages folder even though they are 
> already in .buildout/eggs.  This means that I no longer have my other 
> develop eggs in my python path and the pyramid app will no longer work. 
>
> I have temporarily got round this by removing the requires option in 
> setup.py before I do setup.py develop.
>
> Is there a better way? Am I missing something?
>
> I tried specifying install-dir, script-dir and -x to not overwrite scripts 
> but it wouldn't work because it said those folders were not on my 
> pythonpath.
>
> How do I get setup.py to recognise that the eggs are already installed 
> somewhere else?
>
> Thanks
>

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/d/optout.

Reply via email to