Grievance: Coming from the JavaScript ecosystem, dealing with Poetry feels like a step back /u/Own-Roadride Python Education

I come from the JavaScript ecosystem, and managing dependencies and running scripts there is relatively straightforward. However, after switching to Python and using Poetry, I’ve encountered some frustrations that I want to share:

• In the JavaScript ecosystem:

  • Running yarn dev or npm start automatically sets up everything — from managing dependencies to executing scripts.
  • It abstracts away much of the setup and configuration, making it very convenient to start coding immediately.

• In the Python ecosystem with Poetry:

  • Every time I want to run a script, I need to manually create a virtual environment and then use poetry run python folder/file.py.
  • This process feels more tedious compared to the simplicity of yarn dev or npm start in JavaScript.

• While I understand Poetry’s benefits:

  • Poetry’s explicit handling of virtual environments ensures proper isolation of dependencies, which is great for Python projects.
  • However, coming from the JavaScript world, I find it frustrating that I can’t just run a single command like yarn dev to get everything up and running.

My question: – Has anyone else felt this way when moving from JavaScript to Python? – How do you manage to streamline this workflow or make it more seamless? – Are there any best practices to make this process less cumbersome?

I come from the JavaScript ecosystem, and managing dependencies and running scripts there is relatively straightforward. However, after switching to Python and using Poetry, I’ve encountered some frustrations that I want to share:

• In the JavaScript ecosystem:

  • Running yarn dev or npm start automatically sets up everything — from managing dependencies to executing scripts.
  • It abstracts away much of the setup and configuration, making it very convenient to start coding immediately.

• In the Python ecosystem with Poetry:

  • Every time I want to run a script, I need to manually create a virtual environment and then use poetry run python folder/file.py.
  • This process feels more tedious compared to the simplicity of yarn dev or npm start in JavaScript.

• While I understand Poetry’s benefits:

  • Poetry’s explicit handling of virtual environments ensures proper isolation of dependencies, which is great for Python projects.
  • However, coming from the JavaScript world, I find it frustrating that I can’t just run a single command like yarn dev to get everything up and running.

My question: – Has anyone else felt this way when moving from JavaScript to Python? – How do you manage to streamline this workflow or make it more seamless? – Are there any best practices to make this process less cumbersome?