[Python-Dev] Re: On the migration from master to main

On 5/3/2021 9:27 PM, Terry Reedy wrote: On 5/3/2021 7:45 PM, Tim Peters wrote: I'm guessing it's time to fiddle local CPython clones to account for master->main renaming now? Blob 2 ("upstream"): """ The CPython repository's default branch was renamed from ``master`` to ``main`` after

[Python-Dev] Re: On the migration from master to main

On 5/3/2021 7:45 PM, Tim Peters wrote: I'm guessing it's time to fiddle local CPython clones to account for master->main renaming now? If so, I've seen two blobs of instructions, which are very similar but not identical: Blob 1 ("origin"): """ You just need to update your local clone after

[Python-Dev] Re: github and dependabot

On Mon, May 3, 2021 at 9:15 PM Łukasz Langa wrote: > It's bogus automation, you can safely reject those pull requests. If you > do merge any pull requests to `main` of your personal fork, your `main` > branch will diverge from python/cpython's. Not recommended. > > I just merged the equivalent

[Python-Dev] Re: github and dependabot

It's bogus automation, you can safely reject those pull requests. If you do merge any pull requests to `main` of your personal fork, your `main` branch will diverge from python/cpython's. Not recommended. I just merged the equivalent pull requests from dependabot on python/cpython. You can

[Python-Dev] github and dependabot

I have two pull requests against my cpython fork from a dependabot -- what is that, and should I merge them? -- ~Ethan~ ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org

[Python-Dev] Re: On the migration from master to main

> On 4 May 2021, at 02:04, Łukasz Langa wrote: > > Having renamed the branch in my fork first, the exact sequence I used on my > own clone was: > > ❯ git checkout master > ❯ git branch -m master main > ❯ git fetch origin > ❯ git branch -u origin/main main > ❯ git remote set-head origin -a > ❯

[Python-Dev] Re: On the migration from master to main

On May 3, 2021, at 19:45, Tim Peters wrote: > Blob 1 ("origin"): > > """ > You just need to update your local clone after the branch name changes. > From the local clone of the repository on a computer, > run the following commands to update the name of the default branch. > > $ git branch -m

[Python-Dev] Re: On the migration from master to main

> On 4 May 2021, at 01:45, Tim Peters wrote: > > Right? Wrong? Do we need some mix of both? Something else? Having renamed the branch in my fork first, the exact sequence I used on my own clone was: ❯ git checkout master ❯ git branch -m master main ❯ git fetch origin ❯ git branch -u

[Python-Dev] Re: On the migration from master to main

I'm guessing it's time to fiddle local CPython clones to account for master->main renaming now? If so, I've seen two blobs of instructions, which are very similar but not identical: Blob 1 ("origin"): """ You just need to update your local clone after the branch name changes. >From the local

[Python-Dev] [RELEASE] Python 3.8.10, 3.9.5, and 3.10.0b1 are now available

This has been a very busy day for releases and on behalf of the Python development community we’re happy to announce the availability of three new Python releases. Python 3.10 is now in Beta Get it here: Python 3.10.0b1 Python 3.10 is

[Python-Dev] Re: [python-committers] [Release manager team communication] master blocked until 3.10 beta 1 is released

On Mon, May 3, 2021 at 5:13 PM Victor Stinner wrote: > Hi, > > Please don't attempt to merge PRs until the GitHub issue described > below is solved ;-) > > Pablo renamed the default "master" branch to "main" (in a live Twitch > stream ;-)) but got a GitHub internal error! Maybe it's because the

[Python-Dev] Re: [python-committers] [Release manager team communication] master blocked until 3.10 beta 1 is released

Hi, Please don't attempt to merge PRs until the GitHub issue described below is solved ;-) Pablo renamed the default "master" branch to "main" (in a live Twitch stream ;-)) but got a GitHub internal error! Maybe it's because the dialog announced that 1.4k+ pull requests and 700+ repositositories

[Python-Dev] [Release manager team communication] master blocked until 3.10 beta 1 is released

Hi everyone, Unfortunately, the CI for master is currently quite unstable and he had some problems that we have been fixing all weekend and today. We are doing our best to stabilize the test suite and making sure that everything is ready to go for the release with no issues, but this will take

[Python-Dev] Re: Announcing the CPython Docs Workgroup

Raymond, Anyone can contribute to the documentation and comment, and core devs can accept patches. Nothing changes here. The Steering Council did approve the initial members and charter. The intent has always been to be transparent and open. As discussed at last year's Language Summit, the goal

[Python-Dev] Re: Announcing the CPython Docs Workgroup

That seems exclusionary. Right now, anyone can contribute to documentation, anyone can comment on proposals, and any core dev can accept their patches. In the interest of transparency, can you explain why the other initial members did not need to go through an application process? ISTM the