> `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"
Last I used poetry was a couple of years ago, and IIRC it didn't gel well with Conda environments.
VS Code is probably one of the top five options, but not mentioning PyCharm as one of the top choices is not right.
There’s a significant difference between a general purpose pluggable code editor, such as VC Studio, Atom, Sublime… and actual IDE made for Python.
Glad you found your happy place, that matters more than the actual feature set provided, IMO.
Eh? Do you mean pycharm? Even so what's wrong with a professional product being paid-for and closed source? Developers have to eat too, many of which I'd imagine also contribute to other opensource projects, using... pycharm.
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.
The whole "open" source system is marching backwards towards inscrutable IDEs that do work by magic and leave the user clueless.
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 hardest thing about learning to program. I'm so sorry."
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.
I've never become a Python fan, but I really don't think it's even usable without virtual environments.
But as a software project, Python is mayhem. pip+pypi is an embarrassment. After the difficult 2.x -> 3.x transition, the 3.x->3.8 period inflicted a world of pain on anyone trying to develop and deploy stable tooling.