Local, dev (C++ built) dependencies #2186
Unanswered
gpetrovic-meltin
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
What is the appropriate way of including local, dev dependencies (edit mode)?
We have a Python project with some internal dependencies that we keep as Git(hub) submodules. Out of the two submodule dependencies, one of them is a pure Python dependency, while the other includes C++ code as well (pybind is used to create a Python module out of it).
Here's how our current setup looks like:
It's very common to work on the submodules while developing the main project, so I've listed the same submodules in both
dependencies
anddev-dependencies
lists. This meant thatpdm install -d
would update them both without having to effectively nuke the.venv
folder each time.However, I'm not sure this is the right approach, and I've noticed that the C++ dependency is built from scratch each time - which is quite time consuming. I also don't think this was documented - I found it by trial and error and later rediscovered a similar solution here.
With Pipfile, it was enough to list the dependency once, and even consecutive
pipenv install
was sure to update it. Most C++ builds were also incremental from what I could see - they were pretty fast.Beta Was this translation helpful? Give feedback.
All reactions