Replies: 1 comment 1 reply
-
So my new observation is, that I can use
to have only one virtualenv as I need. But I still have problem to add package to |
Beta Was this translation helpful? Give feedback.
1 reply
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.
-
I have the following structure of the project(with old requirements.txt managed by hand and installed by pipy):
core_package -> standalone project, with separate git and own requirements.txt(most of the packages)
project_specific_package -> project that needs core_package to live, and have own requirements.txt i.e.
I can add requirements.txt to core_package and project_specific_package when developing these things.
The project structure is:
Is it possible somehow create just one virtualenv in root of project_specific_package? and when I run rye sync inside core_package/ it will generate core_package/requirements.lock just from core_package/pyproject.toml
I tried to use following pyproject.toml:
And when I run
rye sync
it works like expected it will generate requirements.lock with all dependencies from core_package and it will install it to virtualenv. What if I want to add package to core_package ? If I navigate to core_package and runrye add
it just won't work.One more experience with pip-tools, that I also tried and I am in beginning of using it. I am managing dependencies only in core_package and when I want to generate core dependencies I simply run
pip-compile --resolver=backtracking --upgrade -o sbcore/requirements.txt sbcore/pyproject.toml
. Is it maybe some option to define source of pyproject.toml with some switch ?Thanks.
Beta Was this translation helpful? Give feedback.
All reactions