Hi Martin, Virtualenv is use for using different version of python or python library so it wont use the default python in system. So when open eclipse for editing, no need to activate virtualenv, but when you need to run the code in specific python install, you need to activate virtualenv.
VIrtualenv will be usefull in production , where several different python version needed or several python libarary with different version used. Regards, Mulianto http://muliantophang.blogspot.com On Mon, Jul 21, 2014 at 2:40 PM, Martin Torre Castro <mad...@gmail.com> wrote: > Firstly, I want to say "thank you" to you, Thomas. > > Secondly, could you or someone how does the development cycles work with > virtualenv? Is this way of working just as I wrote? > > I think it works by activating the virtualenv every time with a "source > activate" command and after that starting to program from the terminal. I > need to know this for adapting Eclipse to activating the virtualenv every > times it opens if virtualenv works as expected. > > Thanks > > > > On Sunday, 20 July 2014 04:29:53 UTC+2, Thomas wrote: >> >> On 7/19/14 6:41 PM, Martin Torre Castro wrote: >> >> Hello, >> >> my name is Martin and I'm a computer engineer from Spain. I'm going to >> start a new project with a colleague and I decided to use Django because we >> searched for free opensource tools and I'm in love with Python. >> >> We have made a couple of tutorials (the official one and "Tango with >> django"). I've also bought the book "Two scoops of Django" for the 1.6 >> Django edition. We're starting the project soon as well as we finish the >> design, but I'm concerned about setting up the new environment. We're >> thinking of using: >> >> >> - postgresql >> - Python/Django [ of course ;-) ] >> - Eclipse/Pydev >> - Git >> - jQuery >> >> >> All good choices. pip and virtualenv provide for a reproducible and >> robust installation. PostgreSQL is imho far superior to other options for >> db. I don't have experience with using Eclipse in this environment so can't >> comment there. >> >> hth >> >> - Tom >> > -- > 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+unsubscr...@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/f99612a0-0d8f-44ee-93ee-2ed3e01055f3%40googlegroups.com > <https://groups.google.com/d/msgid/django-users/f99612a0-0d8f-44ee-93ee-2ed3e01055f3%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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+unsubscr...@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/CA%2BSr5mS_Kk_i0%3DFgO-pfw2e4N_11VXQ6yp%3D0T82X2Qp0zy3dLw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
