My suspicion is that it's a djangorecipe issue (because I've run into it myself). I say this because I seem to recall that if I change the installation dependencies, zc.recipe.egg:scripts will notice that and regenerate the wrapper script. djangorecipe definitely does not. I haven't dug into the recipe to see what they're doing differently (and I haven't taken the time to actually confirm this so I could be insane).
Nathan On Wed, Sep 30, 2009 at 6:27 AM, Chris Withers <[email protected]> wrote: > Tres Seaver wrote: >>> >>> I have a part using the djangorecipe part that stubbornly refuses to >>> notice that I've changed an eggs dependencies or changed the stuff in the >>> develop line of the [buildout] section. >>> >>> I've tried "bin/buildout install djangopart" but this doesn't have any >>> effect. The only way I've found to get the part to re-install is to change >>> the options in the part, install, and then put the options back like I want >>> them before re-installing :-( >> >> $ rm -rf parts/djangopart; bin/buildout > > Does anyone know if this is a problem with djangorecipe or buildout? > > I only *remember* experiencing this with djangorecipe. If it *is* > djangorecipe, anyone know what it's doing wrong? ;-) > > Chris > > -- > Simplistix - Content Management, Batch Processing & Python Consulting > - http://www.simplistix.co.uk > _______________________________________________ > Distutils-SIG maillist - [email protected] > http://mail.python.org/mailman/listinfo/distutils-sig > _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
