The Pyramid docs intentionally don't do this so that in the documentation it is explicit every time the "python" command is invoked that it is coming from the virtualenv. If a user skipped the activate in the tutorial they'd see that we're using "python" all over the place and not understanding that it's actually the executable "bin/python" from the virtualenv. For tutorial purposes I think it's better to be explicit and help users catch their mistakes.
On Tue, Dec 6, 2011 at 5:50 AM, rihad <ri...@mail.ru> wrote: > Hi, all. Why don't Pyramid docs/tutorials mention running $env/bin/ > activate before managing a project (and "deactivate" it when done)? > Many times I've mistakenly run commands like "python setup.py ..." and > the stock system python was taken from the PATH, when I should have > run ../bin/python setup.py. Running "activate" would take care of > this, setting the PATH appropriately. This would also automatically > install new dependencies in the virutalenv directory, not needing root > access. > > TurboGears docs do mention that, that's how I knew they existed. > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To post to this group, send email to pylons-discuss@googlegroups.com. > To unsubscribe from this group, send email to > pylons-discuss+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/pylons-discuss?hl=en. > > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
