Do not process entries from poetry.lock until their category is known

[frenzymadness]

Related Issues and Dependencies

#295

Let's see what this change will break. I expect possible incompatibility with older poetry.

[frenzymadness]

Now is the time to check the failures and see whether the code is wrong or the test is wrong.

[frenzymadness]

There are two kind of breaking changes now:

• Packages are allowed to be in more than one category - the category is either derived from the content of pyproject.toml (for direct dependencies) or from the package with another package as a dependency (to be in the same category).
• Because of the previous point, packages might be mentioned more than once in pipfiles (where it make sense) but we do not allow duplicities in requirements files.

[frenzymadness]

It seems that the new test with complex dependencies is not compatible with Python <= 3.7. Fixed.

[frenzymadness]

This is a big change. A review is necessary. Cc: @fridex @yrro

[frenzymadness]

Does anybody have a plan to do a review?

[fridex]

Does anybody have a plan to do a review?

I had a brief look on changes - it looks like they are well covered by tests. Unfortunately, I don't have time for an in-depth review. Feel free to consider +1 from me. Very nice job and thanks for looking into this! 👍🏻 💯

It would be great if @yrro could verify this patchset on the originally reported issue or provide the related lockfile (if not done already).

[yrro]

I think my pyproject.toml and lockfile made it into the tests for this PR. But I hope I can give it a manual test on my proejct some time this week.

[frenzymadness]

Thank you both. Sam is correct - his configuration is now part of the tests.

[frenzymadness]

Or we can test it out there in the wild with a new release 🤔

[frenzymadness]

All right, let's give it a try.