And even more data:
I added a body to the PR I was originally having trouble with:
button stayed gray
I went away for a while, say 5 - 10 minutes, and when I went back to
that screen the button was green. I created the PR.
--
~Ethan~
___
Python-D
On 9/21/20 6:09 PM, Ethan Furman wrote:
The green "create pull request" button is greyed out.
I've tried reselecting the repos and branches, logging out and in,
navigating to that screen via my own repository -- nothing is working.
I have more data:
I pushed another branch and opened the li
Is this still problem? Which fork/branch did you did you want to create to
the PR with?
On Mon, Sep 21, 2020, 6:14 PM Ethan Furman wrote:
> The green "create pull request" button is greyed out.
>
> I've tried reselecting the repos and branches, logging out and in,
> navigating to that screen
On Sep 21, 2020, at 21:09, Ethan Furman wrote:
> The green "create pull request" button is greyed out.
>
> I've tried reselecting the repos and branches, logging out and in, navigating
> to that screen via my own repository -- nothing is working.
>
> Any ideas?
I tried creating a PR from a bra
The green "create pull request" button is greyed out.
I've tried reselecting the repos and branches, logging out and in,
navigating to that screen via my own repository -- nothing is working.
Any ideas?
Thanks.
--
~Ethan~
___
Python-Dev mailing lis
On Fri, Sep 18, 2020 at 10:42 PM Guido van Rossum wrote:
> At the same time it's as old as Python -- for most builtins other than
> strings, repr() and str() are the same, and modeled after repr().
> Historically, I only introduced the difference between str() and repr()
> because of strings --
On 9/19/20 2:08 PM, Guido van Rossum wrote:
I'm just trying to present an argument that if the str() of an enum was
its name and the repr() was its "full name" (at least including the
class) that would be pretty sweet.
Well, we're still early enough in the 3.10 cycle we can make that change
On Mon, 21 Sep 2020 20:35:33 +0200
Victor Stinner wrote:
>
> When I proposed my PEP 620 "Hide implementation details from the C
> API", I was asked about a proof that the PEP unlocks real optimization
> possibilities. So I wrote an implementation of tagged pointers:
> https://github.com/vstinner/
Hi,
I need to help to attempt to optimize my experimental CPython fork
which uses tagged pointers.
When I proposed my PEP 620 "Hide implementation details from the C
API", I was asked about a proof that the PEP unlocks real optimization
possibilities. So I wrote an implementation of tagged pointe
