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

Archive the typed-ast repository #200

Closed
hauntsaninja opened this issue Jul 1, 2023 · 5 comments
Closed

Archive the typed-ast repository #200

hauntsaninja opened this issue Jul 1, 2023 · 5 comments

Comments

@hauntsaninja
Copy link

hauntsaninja commented Jul 1, 2023

I've been maintaining https://github.com/python/typed_ast. We announced the death of the project about two years ago: python/typed_ast#179. The functionality this library aimed to provide got mostly subsumed into the standard library in Python 3.8 and we've transitioned all of its biggest users away from the project. And of course, the code on PyPI continues to be functional for any current users on current Python versions (including 3.12 beta).

In https://discuss.python.org/t/new-python-organization-repository-policy/17376 , the Steering Council reaffirmed its purview over the birth of repositories in the Python org, so I'm assuming you're also interested in the death of repositories :-) I also don't have the ability to archive the repo and I'm not exactly sure who does.

@gpshead
Copy link
Member

gpshead commented Jul 2, 2023

Its EOL has been announced and it'll remain up on PyPI, I suggest @ambv just go ahead and archive the project on Github (I believe @ambv has permissions to do that?). No need to wait for the SC as I believe it is equally easy to unarchive if further maintenance were ever desired. It is also easy to fork an archived repo into a non /python/ org for further maintenance AFAIK.

@hugovk
Copy link
Member

hugovk commented Jul 2, 2023

Before archiving, I suggest editing the README to put a prominent notice that it's EOL.

(You could optionally release it to PyPI so it shows there too, and if so, could use the Development Status :: 7 - Inactive Trove classifier.)

@gpshead
Copy link
Member

gpshead commented Jul 3, 2023

Yep, (steering council chatted today:) we're fine with this. Please do a final PyPI release update with the docs saying it is EOL and unmaintained, including the trove classifier so that it is clear to people seeing the package on PyPI clearly see that it won't be updated further. Then feel free to archive the Github repo.

@gpshead gpshead closed this as completed Jul 3, 2023
@hauntsaninja
Copy link
Author

Thank you! I've added a notice to the README, the long description, added the classifier and made the final release. I'll wait a few days just in case and then ask Łukasz to archive the repo.

@ambv
Copy link

ambv commented Jul 5, 2023

As it's easy to un-archive if needed, I already did that.

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

No branches or pull requests

4 participants