Re: virtualenv best practice / source control

On Thursday, October 1, 2015 at 5:51:57 PM UTC+5:30, junk wrote:

Greetings wise django users,

Can someone provide a link or description of how to use virtualenv/django/source-control all at the same time?

I thought I would put my virtualenv code, and django, and a starter project in source control.  That was a fail - when the directories moved, nothing worked.

I think it a lot better not to put the virtualenv in source control. All you really need is the requirements.txt in source control and it is fairly easy to set up a  virtualenv.

You can make a virtualenv relocatable, but even then it is likely to cause problems - it is certain to cause problems if it contains any C extensions and someone wants to clone the code on a different OS.  It also bloats your repository with a lot of code that is not specific to your project, and I see little benefit to doing it.

 

I changed some paths & symbolic links, and got some things working, but not everything.

Thanks everyone.

Regards,
Jody

--   This account is used for situtations where I believe SPAM may be sent to me.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/2c5cedfc-cb4e-4b26-9013-21b46f75bc28%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.