Closed eloquence closed 8 months ago
dbc7065ae6f7815e686c904de4bf8feee62fe6a1 is a stab at addressing this more comprehensively by canonicalizing names in our utility functions. However, I want to add some test cases before opening a PR, to ensure it's compatible with all cases we may encounter in the wild.
Even with #474, our current
poetry
logic is still susceptible to inconsistencies in how dependencies may appear inpyproject.toml
andpoetry.lock
.Steps to reproduce
flit_core
inpyproject.toml
Expected behavior
New dependency will be picked up
Actual behavior
flit-core
(which is how it appears inpoetry.lock
) is not picked up