Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

adding initial support for poetry groups, beginning testing #218

Conversation

Gregory-Pereira
Copy link
Member

Related Issues and Dependencies

Addresses Groups support in Poetry lock files #185

This introduces a breaking change

  • Not sure, opening pr while undergoing testing --> /hold

This Pull Request implements

Adding support for poetry dependency groups as introduced in v1.20a2 of poetry (preview version).

Description

Current change is to the parsing of the pyproject.toml file, where it will look for additional groups. Poetry group syntax for dependencies looks like [tools.poetry.group.<group_name>.dependencies]. It also introduces an alternative for the dev-dependencies by defining them as a group, like so: [tools.poetry.group.dev.dependencies], and these are included in the adjustments to the micropipenv.py file. The original issue above mentions that we will need to handle dev dependencies in the poetry.lock file, which I am not sure about, because I thought that was included by checking the "category" of entries in that file are main or dev, and the groups themselves aren't listed in the poetry.lock file.

Original PR started from old version of upstream master, migrated here so there are less changes. Additional ran pre-commit for entire repo, so there are unrelated lining changes in setup.cfg.

@Gregory-Pereira
Copy link
Member Author

/retest

@harshad16 harshad16 removed their request for review January 11, 2022 14:04
@goern
Copy link
Member

goern commented Jan 14, 2022

any updates?

@Gregory-Pereira
Copy link
Member Author

Currently paused, I am finishing up deploying argocd-notifications for operate-first right now, but this is my next priority after that. I need to debug the 4 tests that failed.

@frenzymadness
Copy link
Collaborator

Note that there is a problem currently with pip 9 which seems to no longer work with the latest setuptools so some of the failures might not be caused by your changes. We're gonna fix that soon hopefully in #219 so just a rebase might help then.

@Gregory-Pereira
Copy link
Member Author

It looks like 2 of the three tests that failed here were using pip90, not sure if it's to do with those setup tools errors, ill comb through the logs more carefully, and if so I will wait on #219 merging. One of them is failing with pip latest as well so ill need to see what happened there. And I will make sure to rebase it gets merged, thanks!

@Gregory-Pereira Gregory-Pereira force-pushed the add-support-for-poetry-groups branch from 1cf2791 to 0bd6551 Compare February 4, 2022 04:21
@sesheta
Copy link
Member

sesheta commented Feb 4, 2022

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign frenzymadness after the PR has been reviewed.
You can assign the PR to them by writing /assign @frenzymadness in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sesheta sesheta added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Feb 4, 2022
@goern
Copy link
Member

goern commented Feb 15, 2022

/assign @frenzymadness

@frenzymadness
Copy link
Collaborator

Poetry 1.2 is still in alpha and the last release is from August last year so there is no rush here. On the other hand, in the docs they say:

Any dependency declared in the dev-dependencies section will automatically be added to a dev group.

and

Poetry will slowly transition away from the dev-dependencies notation which will soon be deprecated, so it’s advised to migrate your existing development dependencies to the new group notation.

Which IMO means that our implementation of dev and default groups should be extended to count with more than just these two groups. I'm afraid that this change will mean that our interface will be different for poetry and pipenv.

@frenzymadness frenzymadness marked this pull request as draft February 22, 2022 07:34
@sesheta sesheta added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 22, 2022
@sesheta
Copy link
Member

sesheta commented May 23, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 23, 2022
@frenzymadness
Copy link
Collaborator

@Gregory-Pereira I see that there is new Poetry 1.2.0b2 released 4 days ago. Do you plan to continue with this PR?

@sesheta
Copy link
Member

sesheta commented Jul 10, 2022

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@sesheta sesheta added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 10, 2022
@Gregory-Pereira
Copy link
Member Author

Thanks for the update. I will be picking this back up shortly, just some other work is currently taking priority.
/remove-lifecycle rotten
/remove-lifecycle stale

@sesheta sesheta removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jul 10, 2022
@goern goern closed this May 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants