Support for mutually exclusive dependencies across groups (e.g. path dependencies during development only)
- [x] I have searched the [issues](https://github.com/sdispater/poetry/issues) of this repo and believe that this is not a duplicate. - [x] I have searched the [documentation](https://poetry.eustace.io/docs/) and believe that my question is not covered. ## Question I believe this issue is related to #668 -- or some of the comments therein -- but I believe my workflow / use case is also a little different from the origin of that issue. Here's the background / what I'm trying to accomplish: - I have a large modular python project. It is generally a main application with dependencies on other components that we maintain -- shared libraries, essentially. - Adding a new feature in the main application often involves changing one or more of these shared libraries. - During development, I'd like to be able to experiment with different code in those shared libraries and integration test it with my main application before actually writing tests for / committing / tagging / pushing / etc. the changes to those shared libraries. Here's how I would do this with setuptools / pip: - Ensure that my main application (`my-app` e.g.) has a `requirements.txt` file that has loose enough versions of my shared libraries so that it'll be satisfied by the next version that I'm working on. For example, if `my-app` will use an updated `my-lib1` version 4.1 and `my-lib2` version 1.12.3, I might have the following in`my-app/requirements.txt`: ``` my-lib1 ^4.1 my-lib2 ^1.12.3 ``` - Setup a
Posted by hozn on Jun 14, 2019, 3:34 PM
Tags
Related issues
- I hate that this whole cluster of beliefs exists, but software on my own computer enforcing what I can and can't do for ideological reaso...
- As I replied in another comment[1], it's their software, their choice.
- [Feature] Support external model integration via personal API keys and local LLMs (BYOK)
- > So when head of companies don’t care about quality, they’ll push hard no matter what to have speed.
- Feature request: support multiple named accounts per app/connector
- Support standalone Windows installer (`codex-setup.exe`)
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
support (SaaS)
I hate that this whole cluster of beliefs exists, but software on my own computer enforcing what I can and can't do for ideological reaso...
NewAs I replied in another comment[1], it's their software, their choice.
[Feature] Support external model integration via personal API keys and local LLMs (BYOK)
> So when head of companies don’t care about quality, they’ll push hard no matter what to have speed.
Feature request: support multiple named accounts per app/connector
Support standalone Windows installer (`codex-setup.exe`)
[feature]: Move OIDC back to self-hosted OSS(Plane Free)
I was running about 1000 machines on VMware in my previous career.
Support for mutually exclusive dependencies across groups (e.g. path dependencies during development only)
- [x] I have searched the [issues](https://github.com/sdispater/poetry/issues) of this repo and believe that this is not a duplicate. - [x] I have searched the [documentation](https://poetry.eustace.io/docs/) and believe that my question is not covered. ## Question I believe this issue is related to #668 -- or some of the comments therein -- but I believe my workflow / use case is also a little different from the origin of that issue. Here's the background / what I'm trying to accomplish: - I have a large modular python project. It is generally a main application with dependencies on other components that we maintain -- shared libraries, essentially. - Adding a new feature in the main application often involves changing one or more of these shared libraries. - During development, I'd like to be able to experiment with different code in those shared libraries and integration test it with my main application before actually writing tests for / committing / tagging / pushing / etc. the changes to those shared libraries. Here's how I would do this with setuptools / pip: - Ensure that my main application (`my-app` e.g.) has a `requirements.txt` file that has loose enough versions of my shared libraries so that it'll be satisfied by the next version that I'm working on. For example, if `my-app` will use an updated `my-lib1` version 4.1 and `my-lib2` version 1.12.3, I might have the following in`my-app/requirements.txt`: ``` my-lib1 ^4.1 my-lib2 ^1.12.3 ``` - Setup a
Comments (0)
No comments yet. Start the discussion.