Forums

Python 3.4, Flask, Bash and the working environment

I want to start working on Flask with Python 3.4. I installed Virtualenv in Python 3.4 with Bash.Then I installed Flask,its dangerous,Jinja2,Werkzeug,MarkupSafe. My question is- every time I start to work on Flask using Python 3.4 should I go into Bash and use the command “workon my-virtualenv or possible some other code. Or is everything now completed to work on Python 3.4 and Flask in the virtualenv. Is Python 3.4 now setup to work on Flask?

My thought is that is it set up and ready to go and that the only reason to go to Bash and use Virtualenv would be if I wanted to add something like other modules or apps?

Yes, if you're using a virtualenv for a web app, the main reason to activate it in a console would be to install new modules, but you may also need to do that if you have scripts that you use to manage aspects of your site.

Thank You!

Can you please clarify what you mean by scripts and give me some example?

Scripts like database migrations, or data management commands (maybe adding and deleting users or that kind of thing).