Skip to content
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

drop support for EOL Python 3.5 #137

Closed

Conversation

terencehonles
Copy link
Contributor

No description provided.

@terencehonles
Copy link
Contributor Author

terencehonles commented Jan 20, 2021

@kislyuk looks like you don't allow the test credentials to be provided to PRs. Not sure if that just requires you to re-run the test or how that works. I'm debugging what is likely a forking issue, but I noticed the package doesn't provide support for Python 2 so I figured it should also drop Python 3.5 since that is EoL (it actually was when Python 2 was dropped)

@kislyuk
Copy link
Owner

kislyuk commented Jan 20, 2021

Hi, thanks for your PR. I do not drop support for prior versions nor introduce CI on pre-release versions of Python without a specific need. For example, dropping support for Python 3.5 would be justifiable if we introduced PEP 526 type annotations.

@kislyuk kislyuk closed this Jan 20, 2021
@kislyuk
Copy link
Owner

kislyuk commented Jan 20, 2021

Also - you are correct that AWS credentials are not currently provided to PRs. I'm planning to re-enable that once I verify that the AWS credentials in the test account are appropriately scoped.

@terencehonles
Copy link
Contributor Author

Hi, thanks for your PR. I do not drop support for prior versions nor introduce CI on pre-release versions of Python without a specific need. For example, dropping support for Python 3.5 would be justifiable if we introduced PEP 526 type annotations.

I'm not sure I get not adding a test on pre-release. It may not fail and if it doesn't fail it makes sense to make sure there are no forwards incompatible changes.

@terencehonles
Copy link
Contributor Author

Hi, thanks for your PR. I do not drop support for prior versions nor introduce CI on pre-release versions of Python without a specific need. For example, dropping support for Python 3.5 would be justifiable if we introduced PEP 526 type annotations.

@kislyuk Do you mind re-opening this then?

@kislyuk
Copy link
Owner

kislyuk commented Jan 22, 2021

I'm not sure I get not adding a test on pre-release. It may not fail and if it doesn't fail it makes sense to make sure there are no forwards incompatible changes.

I appreciate the effort, but I will not add pre-release versions of Python to the CI for this project. It creates more work for me for an uncertain benefit. If a Python version is released that is incompatible with watchtower, we will deal with it then.

@kislyuk Do you mind re-opening this then?

Can you clarify why you think this PR should be reopened?

@terencehonles
Copy link
Contributor Author

@kislyuk because I already add types to this branch and you can't see that because this PR is closed.

@kislyuk
Copy link
Owner

kislyuk commented Jan 23, 2021

OK, please open a new PR with the type hints and dropping Python 3.5.

@kislyuk
Copy link
Owner

kislyuk commented Jan 30, 2021

@terencehonles are you still interested in reopening the PR? I am happy to merge type hint support if you have the time to finish this up. Otherwise please let me know and I can pull from your fork to see if I can finish it up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants