On Tue, Feb 7, 2017 at 11:38 PM, Victor Stinner
wrote:
> I know that different people have different expectation on GitHub. I
> would like to take the opportunity of migrating to Git to use the
> "author" and "committer" fields. If the author is set to the real
> author, the one who proposed the c
2017-02-08 8:35 GMT+01:00 Victor Stinner :
> I'm sure the patch author would appreciate it, but I don't think we
> need to require it as we have gone this long without it.
I know that different people have different expectation on GitHub. I
would like to take the opportunity of migrating to Git to
(Oops, I wrote privately to Brett, so he replied me in private. So
here is a copy of our emails.)
Brett Cannon via gmail.com
On Tue, 7 Feb 2017 at 13:42 Victor Stinner wrote:
>
> If I push a patch file written by someone else, should I try to use the
> author full name + email?
I'm sure the pat
On Feb 7, 2017, at 17:19, Edward Ned Harvey (python)
wrote:
> I would like to suggest that the OSX installer automatically run "Install
> Certificates.command", or display a prompt to users saying "Run Now" during
> installation.
Thanks for your suggestion. Please open an issue for this on ou
I would like to suggest that the OSX installer automatically run "Install
Certificates.command", or display a prompt to users saying "Run Now" during
installation.
Having the readme is helpful - but only after you google for 20 minutes,
because of an exception you encountered. Of course nobody
On Feb 07, 2017, at 02:15 PM, Mike Miller wrote:
>Does anyone know why Python 3.6 is not the default Python 3 under the
>upcoming Ubuntu Zesty, or what may be holding it back?
I guess that would be me. :)
>Is there anyone that could give it a nudge? It's in the repos but not as
>python3:
>
>htt
Hi,
Does anyone know why Python 3.6 is not the default Python 3 under the upcoming
Ubuntu Zesty, or what may be holding it back? Is there anyone that could give
it a nudge? It's in the repos but not as python3:
http://packages.ubuntu.com/zesty/python3
http://packages.ubuntu.com/zesty/python
On Tue, 7 Feb 2017 at 11:17 Jim F.Hilliard wrote:
> That's great, congratulations! I believe this change will make it way
> easier for people to get involved!
>
> A small question, since people can now submit new issues via pulls instead
> of going to bugs.python.org, what will be the purpose of
Nice, good news.
On 02/07, Brett Cannon wrote:
To let the non-core devs know, the GitHub migration will be happening this
Friday. For those of you who use the current GitHub mirror to create
patches, do be aware that the hashes will most likely be changing so don't
expect your checkout to work
That's great, congratulations! I believe this change will make it way
easier for people to get involved!
A small question, since people can now submit new issues via pulls instead
of going to bugs.python.org, what will be the purpose of the latter?
As I skimmed through cpython-devguide.readthedoc
2017-02-07 10:03 GMT-08:00 Brett Cannon :
> To let the non-core devs know, the GitHub migration will be happening this
> Friday. For those of you who use the current GitHub mirror to create
> patches, do be aware that the hashes will most likely be changing so don't
> expect your checkout to work
To let the non-core devs know, the GitHub migration will be happening this
Friday. For those of you who use the current GitHub mirror to create
patches, do be aware that the hashes will most likely be changing so don't
expect your checkout to work past Thursday (you can always generate a patch
and
12 matches
Mail list logo
