On 16/09/2010 12:06pm, Nick wrote:
Yes and no. I'm familiar with the term but haven't read up on it
enough to wrap my head around installing it and getting it setup. Is
it absolutely essential to get used to working with virtualenv if you
plan to develop on a Windows machine but your production servers are
running *nix?
I do that and it works ok <disclaimer> but I don't know whether it is
best practice.</disclaimer>
I don't use virtualenv although it seems like a good way to segregate
stuff for different python versions. I don't currently have a need for
it so it is on the future list for me. Back to your "Is it absolutely
essential" question ...
No.
I always install third party apps with "setup.py install" which puts
them in the correct respective site-packages directories on both Windows
and Linux and they "just work".
I use my own source directory on Windows for my own django apps and they
all play together on both platforms without much current thought on my part.
The trick is to automate delivery of your own source to the linux web
server directory you have chosen. I think it would complicate things
incredibly to try and manage third party source delivery at the same time.
I use subversion hook scripts to trigger svn export into the chosen
directory every time I commit a source change on Windows. At this point
I must say the linux machine I'm using is a staging server not a
production server. It doesn't matter if something goes belly-up. In fact
when the unit tests fail it is usually because I haven't installed or
updated a third party package on the linux machine.
Finally, I put a shortcut to the site-packages directory in the same
directory as my settings.py file so I can visit third-party source
whenever I feel like it.
hth
Mike
On Sep 15, 9:50 pm, "[email protected]"<[email protected]> wrote:
Nick,
yes...and no.
Have you looked at using Virtualenv?http://pypi.python.org/pypi/virtualenv
On Thu, Sep 16, 2010 at 1:44 AM, Nick<[email protected]
wrote:
Let's say you have Python installed to D:/dev/python2.6
Is it wise/common practice to put django and other third party python
libraries (like pygments or markdown) in the python2.6/Lib/site-
packages/ directory while putting your actual projects in a completely
separate location off the python path?
I ask because I want to get used to placing my python install, django
install, third party python libs, django projects, and django
applications in a familiar/standard path structure so migrating to
various web hosts will be as painless as possible plus well organized.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected]<django-users%2bunsubscr...@googlegroups.com>
.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
--
Guadajuko! Vamos a correr!
-"Cool! we are going to run!"
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
