2 ms·
Hm, yeah, that definitely sounds like a resolver bug. Did you report it? I'm curious to see if it was fixed.
by stavros 5y ago
Hm, yeah, that definitely sounds like a resolver bug. Did you report it? I'm curious to see if it was fixed.
- bigbillheck 5y agoI did not report it because I found somebody else had already reported it and it was a WONTFIX (for reasons I don't immediately recall).
- code_biologist 5y agoI suspect in GP's case there was something blocking the intersected range. That should work perfectly. The poetry author doesn't want to support package version range overrides like yarn does [1]. His call I suppose, but I think it's the one major flaw in the otherwise giant step that poetry takes forward. [1] https://github.com/python-poetry/poetry/issues/697 https://github.com/python-poetry/poetry/issues/697