Closed anshumanb closed 11 years ago
I don't use pydev myself, but I've just asked two pydev-using colleagues about this.
Nice! I think two control-scripts are indeed the way to go. Passing initialization
is a very clean solution.
I think this is a nice addition to django recipe.
Please submit the pull request. If you include passing unittest it will be accepted and released quicker.
Thank you for your pull request that includes a test. This is very helpful. There is one thing I want to make sure before merging the pull request.
I'm not getting this buildout part: [pydev] =<django initialization = ...
I'm unfamilliar with the =< syntax and when I include this in my buildout the initialization code didn't end up in the bin/django script.
Try <=
(instead of =<
). This Buildout quick reference card has a section on cloning parts using <=
.
Ah, thanks for learning me something new.
I've merged the pull request. Before a release is done of a new djangorecipe version I want to include the initialization to the wsgi, fcgi and test scripts too.
You're welcome.
JJmurre fixed this in #60
I'm using Pydev with its Django support for my Django project. Running Django with auto-reload in Pydev requires adding a small snippet of code
just before the
if _name_ == "_main_":
in the manage.py module (or in this case the control-script that is generated).If Djangorecipe provides an
initialization
option, which would get passed as a parameter directly tozc.buildout.easy_install.scripts
, creating a control-script for Pydev would be dead-simple. Something like the following could then be used to generate two control-scripts, one for command-line usage and one for Pydev:I can submit a pull request if this enhancement gets accepted.