Earlier quoted context omitted.
Virtual environments are, sadly, absolutely crucial for Python beginners to get their heads around if they are to do anything more advanced then "hello world". When I'm getting someone started I usually say: "There is a magic incantation involved in Python development called 'activating your virtual environment' - if stuff isn't working as you expect, check that you have done this. Development environments are the ha…
pip freeze > requirements.txt When first learning python and virtual environments, it took me a little bit of time to understand that the virtual environment is basically a clean slate. The command above saved a lot of time. I’d go so far as to having a set of requirements files ready to go for certain types of projects just to get started.
Modern Python Developer's Toolkit
21–24 of 24 posts
Check out pipenv, it really is a lot simpler.
Re: Modern Python Developer's Toolkit
#22> modern > `setup.py` / `setup.cfg` / `requirements.txt` Yeah... no. Considering there are tools like Poetry and `pyproject.toml` superseding setup.*, I wouldn't call the aforementioned "modern"
I personally use Setuptools (.py and .cfg) with pyproject.toml for the build settings.
Last I used poetry was a couple of years ago, and IIRC it didn't gel well with Conda environments.
Re: Modern Python Developer's Toolkit
#23Title could be more helpful if it included "(video)". Then I would not have clicked through.
It's not just a video. There is a table of contents on the left side with the links.
Re: Modern Python Developer's Toolkit
#24Title could be more helpful if it included "(video)". Then I would not have clicked through.
It's not just a video. There is a table of contents on the left side with the links.
Good point, I didn't realise that.
Not sure if many others made the same assumption, but that landing page feels to me like it should have a more obvious way to feed into the text-based content.