-
Notifications
You must be signed in to change notification settings - Fork 8
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
#17 add pathdep remover #19
Conversation
def handle(self) -> int: | ||
path_dependency_remover = PathDependencyRemover() | ||
path_dependency_remover.update_dependency_group( | ||
self.io, self.poetry.pyproject, self.poetry.package.dependency_group("main") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
S (Substantive): this is probably fine for this version, but we likely would need to be able to handle when export is called with other groups with the --with <groups>
option too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Curious how the build/publish rewrite was working with the monorepo group, given it uses a very similar implementation.
Poetry path-based dependencies defined under the monorepo dependency group will fail to be resolved upon export on any machine that is not the one on which the original export was performed.
In order to prevent such dependency resolving failures, it is needed to extend poetry's export command such that any path-based dependencies are not included in the resultant requirements.txt.