export: replace in-tree implementation with poetry-plugin-export

[abn]

Once the export plugin code releases 1.x (python-poetry/poetry-plugin-export#46), this PR should add changes to replace the export command.

Closes: #4824
Depends-on: #5412

Notes:

• Maintain commits when merging.
• Reviewing per commit might be easier.

[radoering]

Before merging this PR, there are some issues in poetry-plugin-export that should be fixed. (Its tests ran against the old in-tree implementation!)

See python-poetry/poetry-plugin-export#50 for proposed changes.

However, the poetry-export-plugin PR is blocked by #5435 which should be merged into master first. Then, this branch can be rebased and python-poetry/poetry-plugin-export#50 can be updated to pass the tests.

Further, there is a change in behavior that I am not sure is intentional: The in-tree export command did not export dev dependencies by default. There was even a test for that default behavior. The poetry-plugin-export exports all non-optional dependencies (including dev-depdendencies) by default.

[abn]

Thanks @radoering. Ugg; good catches. As for the beaviour change, I commented on the python-poetry/poetry-plugin-export#50. I need to take a closer look at #5435, first glance reminds of #5311 (comment).

[radoering]

I think there two open points that build on each other:

1. decision on default behavior (including --with/--without handling), see latest changes in Fix 1.0.0 issues poetry-plugin-export#50 for the variant "no breaking change but different behavior of export command compared to install command"
2. update documentation (should be done after decision on default behavior was made) btw, the documentation has to remain in this repo?

[abn]

poetry-plugin-export==1.0.1 should fix the issues. I have also added an additional test run to verify everything works.

[radoering]

2. update documentation (should be done after decision on default behavior was made) btw, the documentation has to remain in this repo?

Still needs to be done.

[abn]

Ack, will update.

Until we have a better strategy for handling this, documentation should remain in this repo as the current website publishing only accounts for this repository. But, in the mid-term (outside of this PR), figure out how to get the website to also support any documentation we put in the plugin repository.

The export plugin is a snow flake at the moment, so handling it as is for now is okay I reckon. But if we start adding more "bundled" plugins, we should come up with a better solution sooner.

Resolved.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.