#2289 Migrate to Poetry

[Gavinok]

This PR resolves #2289

I migrated the use of requirements.txt and setup.py over to poetry. The use of multiple requirements.*.txt is replaced with dependency groups in the pyproject.toml. I have also added a dedicated [tool.poetry.group.test.dependencies] as opposed to the original requirements.dev.txt which contained both developer dependencies and testing dependencies.

[dbluhm]

I believe we want to install the dependencies for askar, bbs, and indy (though this one should go away very soon) as extras rather than as groups. From the poetry documentation:

Dependency groups, other than the implicit main group, must only contain dependencies you need in your development process. Installing them is only possible by using Poetry.

To declare a set of dependencies, which add additional functionality to the project during runtime, use extras instead. Extras can be installed by the end user using pip.

[usingtechnology]

Works great - awesome job.

Can we add a Poetry.md file in the root of the project that provides a cheat sheet for developers that have not used poetry before? Particularly around virtual envs and usage for running tasks through poetry or not using virtual envs. Also, should explain where and how poetry is used to build and publish the library.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[usingtechnology]

pinging @dbluhm for a final approval.

[swcurran]

@Gavinok -- a question for you about this PR. We discovered that the problem with the Aries Agent Test Harness that was triggered by this PR was the removal of the "bin/aca-py" shell script. From scanning the commits, it looks like that was done deliberately, but I wanted to confirm that, and the rationale for the change. It is a breaking change we'll need to document in the changelog in case anyone (like AATH) is using the file. Do you think it would be a bad thing to put the file back or in changing to poetry should it be removed?

I see these two commits where the change was made:

• Dropped dedicated aca-py script for poetry calling of main()
  ff377ec
• bin directory is no longer necessary

Thanks!

[Gavinok]

@Gavinok -- a question for you about this PR. We discovered that the problem with the Aries Agent Test Harness that was triggered by this PR was the removal of the "bin/aca-py" shell script. From scanning the commits, it looks like that was done deliberately, but I wanted to confirm that, and the rationale for the change. It is a breaking change we'll need to document in the changelog in case anyone (like AATH) is using the file. Do you think it would be a bad thing to put the file back or in changing to poetry should it be removed?

I see these two commits where the change was made:

• Dropped dedicated aca-py script for poetry calling of main()
  ff377ec
• bin directory is no longer necessary

Thanks!

This may be a misunderstanding on my part of what poetry did with its scripts functionality. We should be able to add the original script back into the repository. The idea was that the [tool.poetry.scripts] entry in the pyproject.toml would replace it once installed.

[swcurran]

OK — could you do a quick and dirty PR to add it back? If it is safe enough, let’s just put it back and not have to explain it to someone. It was tougher than it should have been to find in AATH.

[Gavinok]

Sure thing, I can't say with 100% confidence that it will work in all cases but clearly the current solution isn't helping filling it's place