Unfortunately, venv doesn't give me a choice as to where the files are stored. They are all under the top directory of the same name as the project but are actually in the same directory as the top level project folder. ie /root/archive/ venv files, and archive/ project. From what you say, they should not be included in the git source control.
Gary R
On 12/11/2015 02:51 PM, Tim Graham wrote:
Gary R
On 12/11/2015 02:51 PM, Tim Graham wrote:
I don't know of a use case where virtualenvs are stored in source control. I wouldn't recommend putting the virtual environment in your project folder either. If you use a tool like virtualenvwrapper [1] you can store all your virtualenvs in a single directory on your system to make managing them easy.--
[1] https://virtualenvwrapper.readthedocs.org/
On Friday, December 11, 2015 at 4:08:29 PM UTC-5, Gary Roach wrote:Since Python3, venv seems to be preferable to virtualenv. Most of the
howto's are for virtualenv. The file setup between the two is completely
different. So do I include the bin/, include/, lib/, and the lib64 ->
/root/archive/lib files in the git repository or should they be
excluded. If the need to be excluded, how.
This is a Django 1.8, Python3.4 project, Debian 8 (jessie) project.
Gary R
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/0aa43312-1070-4c21-94ca-4a39cd15096a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment