Skip to content
Advertisement

Tag: dependency-management

Why can’t I install a Python package with the Python requirement “>=3.8,<3.11" into a Poetry project with the Python version "^3.9"?

I’m having an issue installing dependencies into my Poetry project. If I run poetry new (as described in https://python-poetry.org/docs/basic-usage/), I can create a new project: My project structure looks like this after I delete a few files not needed for this reproduction: My pyproject.toml file looks like this: When I run poetry add scipy, it tries to install the latest

Dependencies of Django Project

I created a setup.py and setup.cfg like explained in the Django docs. Now I am unsure how to add dependencies to my project. If someone installs my code, other tools like Pillow should automatically get installed. I read that install_requires is the right way (not requirements.txt), but how to specify this? The file setup.py looks pretty generic, and all content

How can I specify requirements for development separately from actual application dependencies? In a Python project and in general?

We have dependencies required for local development that we’d like to specify in our project for the sake of other developers. These dependencies are not actually required by the application though. In python we specify dependencies that the app need in a requirements.txt. What is the best practice for specifying/pinning development specific (not required by the app) dependencies and packages?

Advertisement