-
Notifications
You must be signed in to change notification settings - Fork 6
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
Address deprecations, update coding conventions, use git-based versioning #19
Conversation
…pre None using boolean comparison
@@ -1,19 +1,32 @@ | |||
name: main | |||
name: pymetalink Testing Suite |
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.
Rename breaks pull request validation rules, please revert
env: | ||
TWINE_USERNAME: ${{ secrets.PYPI_USERNAME }} | ||
TWINE_PASSWORD: ${{ secrets.PYPI_PASSWORD }} | ||
POETRY_HTTP_BASIC_FOO_USERNAME: ${{ secrets.PYPI_USERNAME }} |
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.
Foo?
@@ -1,21 +1,21 @@ | |||
The MIT License (MIT) | |||
|
|||
Copyright (c) 2016 Neil McNab, Hampus Wessman | |||
Copyright (c) 2007-2024 Neil McNab, Hampus Wessman, and other contributors |
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.
We need a set of designated copyright holders to make usage decisions, if we open this up we make it impossible to make decisions on licensing without reviewing with all previous contributers
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.
Ah, understood. Would it make sense to add those who have contributed to date, or do we want to leave it to Neil and Bram?
I've also seen people listed for different years, so we could technically add yourself from when you adopted the project?
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.
Adding people makes sense, we cna just have a contributors list and mention those poeple in the copyright statement, that would be fine. Legally it's probably very hard to work with "go look at git to see who contributed to figure out who to contact for copyright issues" 😉
|
||
install: build | ||
dh_testdir | ||
dh_testroot | ||
dh_clean -k | ||
dh_clean -k |
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.
We should split formatting changes into a new pr then rebase, all these tiny changes make it hard to review
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.
I can see about splitting the formatting changes off. Shouldn't be too difficult.
requires = ["poetry-core>=1.2.0"] | ||
build-backend = "poetry.core.masonry.api" | ||
|
||
[tool.black] |
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.
I have been using ruff format a lot lately, it’s a lot fasten so I would prefer that, but a formatter is a good idea and we should push that in a separate pr
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.
I've been using ruff
in a few places as well. I'll verify what the configuration requires so that we solely use that tool instead of black
.
Dear contributor, sorry for the late reply and thank you for taking the time to open up a PR! some changes I agree with, some I would love to split off into a separate pr. I don’t have a laptop this week, but will try to do a proper review next week. Could you consider moving the formatting to a new pr? |
Changes
poetry.lock
file.idea
to.gitignore
(for JetBrains IDEs)twine
, opting for nativepoetry
commandspoetry-version-plugin
DeprecationWarning
message being emitted in newer versions of PythonAdditional context
These are deprecation notices that were being raised in downstream projects:
These have been addressed