-
-
Notifications
You must be signed in to change notification settings - Fork 187
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
Poetry packaging #835
Poetry packaging #835
Conversation
bd6a279
to
0cd508a
Compare
hmm perhaps aioboto should switch to pyproject.toml as well. Sorry really behind in the forward looking PRs, will try to look soon just been super busy since move, or maybe another aioboto admin can chime in =) |
3d034ac
to
e6ae3cc
Compare
26fd5c6
to
32bd40b
Compare
This pull request fixes 5 alerts when merging 32bd40b into 2a7c7f5 - view on LGTM.com fixed alerts:
|
a3aea42
to
12d3d09
Compare
This pull request fixes 5 alerts when merging 12d3d09 into 2a7c7f5 - view on LGTM.com fixed alerts:
|
4c15807
to
b8e8436
Compare
This pull request fixes 5 alerts when merging b8e8436 into 2a7c7f5 - view on LGTM.com fixed alerts:
|
b8e8436
to
b1dc068
Compare
This pull request fixes 6 alerts when merging b1dc068 into ef96004 - view on LGTM.com fixed alerts:
|
c40597a
to
7771889
Compare
- poetry manages all aspects of project metadata and dependencies in pyproject.toml - Pipfile is obsolete - setup.py is obsolete - project might only support python >=3.7,<4.0 now? - tests will not run in python 3.6.x - contributions require python 3.8
7771889
to
ea83ed1
Compare
@dazza-codes given that botocore has swapped to https://github.com/boto/botocore/blob/develop/pyproject.toml seems like this now makes even more sense, thoughts? |
@dazza-codes I rebased on this PR to fix unit tests and linting in my fork: lafrenierejm/aiobotocore@ |
could you work with #975 so we get a PR that includes both aspects? thanks! |
@thehesiod: Would you agree that this PR is stale and may be closed at this point? |
yep agreed, a ton has changed. We should have an issue to discuss this about where we want to head, so many tools |
Closing it for now. Anyone interested in modernizing dependency management and packaging tooling, open an issue or start a discussion. |
Fix #833 although it does not use a lambci docker container in the travis-CI matrix.
This PR is a response to difficulty on a couple of other PRs when I can't grapple with pipenv for my dev-env. There might be bits-n-pieces of this PR that are welcome and other bits that are not. I'm open to discussion, testing and compromises. I'm not having much success with pipenv. Even if this PR is not adopted/merged, I will find it useful to work with this branch and rebase on master and manage a parallel set of poetry-deps as needed.
This is an attempt to use poetry packaging for the project and it might be a contentious PR/issue, depending on dev-team preferences for dev-env setups. In using poetry for the past year or so, this PR represents some patterns that are working consistently for me. Hopefully the added files are mostly self-explanatory, please ask any questions to clarify things and take it for a spin on your local to see how it works out.
TODO