You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Split typing_extensions into a separate repository? #1182
While there is of course the general theme of "basic typing related stuff", I think that typing_extensions is the odd one out here. Its code is basically completely separate from the rest of the repository, tags for typing_extensions make no sense for the rest of the repository (and vice versa), and the issues are quite technical, compared to the more soft "general" issues.
There also have been complaints about notification spam,
I think it would ease maintenance to separate those repositories. For example, it could reduce notification spam for people not interested in typing_extensions.
I'd want to make the new repo python/typing_extensions. I believe we need SC approval to add a new repo to the Python org.
We can use git filter-branch magic to preserve history in the new repo.
The same people can keep commit access to both repos for now. (Though I'd be open to giving more people involved in the typing community access to python/typing in particular.)
I'd want to make the new repo python/typing_extensions. I believe we need SC approval to add a new repo to the Python org.
Could you or @gvanrossum look into this as core developers?
We can use git filter-branch magic to preserve history in the new repo.
We should also be able to create an empty repository, add that as an extra remote of a locally checked out copy, and push. This would essentially duplicate the history between both repositories, keeping history and SHAs intact. Unless I'm missing something.
The same people can keep commit access to both repos for now. (Though I'd be open to giving more people involved in the typing community access to python/typing in particular.)
Since the SC gave its approval, what's the best way forward? Once the repository has been created, I can set it up and create the necessary PRs, but I'm perfectly fine with someone else doing the work. :) Should we use filter-branch as @JelleZijlstra suggested or use the repo split as suggested by me?
I've bulk transferred all closed issues as well, only a few old PRs cannot be moved. I suggest we remove the typing-extensions label as well to avoid confusion, even if it would affect those old PRs.
Activity
gvanrossum commentedon May 12, 2022
Sounds like a good idea (even though I don't have any of those complaints myself and would probably subscribe to the typing_extensions repo as well).
JelleZijlstra commentedon May 12, 2022
Agree that this would be useful. Specifics:
python/typing_extensions. I believe we need SC approval to add a new repo to the Python org.git filter-branchmagic to preserve history in the new repo.srittau commentedon May 12, 2022
Could you or @gvanrossum look into this as core developers?
We should also be able to create an empty repository, add that as an extra remote of a locally checked out copy, and push. This would essentially duplicate the history between both repositories, keeping history and SHAs intact. Unless I'm missing something.
+1
gvanrossum commentedon May 12, 2022
I asked the SC (python/steering-council#126).
srittau commentedon May 18, 2022
Since the SC gave its approval, what's the best way forward? Once the repository has been created, I can set it up and create the necessary PRs, but I'm perfectly fine with someone else doing the work. :) Should we use filter-branch as @JelleZijlstra suggested or use the repo split as suggested by me?
JelleZijlstra commentedon May 18, 2022
I have permissions to create the repo. I can do it later today. I'd prefer to use filter-branch so the history of the new repo is cleaner.
JelleZijlstra commentedon May 19, 2022
https://github.com/python/typing_extensions now exists. Notes on what I did:
git filter-repoto exclude everything buttyping_extensions/and.github/and move the directory to the top levelmainsince that's the new normtopic-typing-extensionstag to the new repoI think that's all that needs to be done, but let me know if I missed something.
Should we announce the new repo somewhere, e.g. on typing-sig?
srittau commentedon May 19, 2022
Thanks, @JelleZijlstra! I think an announcement would be a good idea.
srittau commentedon May 19, 2022
I've bulk transferred all closed issues as well, only a few old PRs cannot be moved. I suggest we remove the typing-extensions label as well to avoid confusion, even if it would affect those old PRs.
JelleZijlstra commentedon May 19, 2022
I also added @hauntsaninja to the new repo and sent an email to typing-sig for visibility. I think that's all, so I'll close the issue.
Gobot1234 commentedon May 20, 2022
I think the GitHub info also needs updating to remove the mention of typing_extensions
srittau commentedon May 20, 2022
Thanks! I've updated the information.