[Python-Dev] GitHub migration scheduled for Friday
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 apply it to a fresh checkout). Otherwise https://cpython-devguide.readthedocs.io/en/github/ is what the devguide will become on Friday if you want to read now instead of waiting for the official switch-over (although for non-core devs the migration basically means you can use GitHub to submit changes instead of uploading patches). ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] GitHub migration scheduled for Friday
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 past Thursday (you can always generate a patch > and apply it to a fresh checkout). Otherwise https://cpython- > devguide.readthedocs.io/en/github/ is what the devguide will become on > Friday if you want to read now instead of waiting for the official > switch-over (although for non-core devs the migration basically means you > can use GitHub to submit changes instead of uploading patches). > > This is great, I'm looking forward to being able to submit pull requests to CPython. Thanks Brett and others for all your hard work on this! > ___ > Python-Dev mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/ > jelle.zijlstra%40gmail.com > > ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] GitHub migration scheduled for Friday
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.readthedocs.io I've see the issue tracker being referenced in certain areas (File a bug section, Reviewing) so I'm not sure I understand how they overlap. ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] GitHub migration scheduled for Friday
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 past Thursday (you can always generate a patch and apply it to a fresh checkout). Otherwise https://cpython-devguide.readthedocs.io/en/github/ is what the devguide will become on Friday if you want to read now instead of waiting for the official switch-over (although for non-core devs the migration basically means you can use GitHub to submit changes instead of uploading patches). ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/stephane%40wirtel.be -- Stéphane Wirtel - http://wirtel.be - @matrixise ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] GitHub migration scheduled for Friday
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 the latter? > The issue tracker is not moving. GitHub will be used for code hosting and pull request management. Tracking bugs and such will stay at bugs.python.org. There's now integration between GitHub and bpo so that if you reference an issue in a pull request a connection will be made on bpo. -Brett > > As I skimmed through cpython-devguide.readthedocs.io I've see the issue > tracker being referenced in certain areas (File a bug section, Reviewing) > so I'm not sure I understand how they overlap. > > ___ > Python-Dev mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/brett%40python.org > ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Py 3.6 on Ubuntu Zesty
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/python3.6 -Mike ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Py 3.6 on Ubuntu Zesty
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: > >http://packages.ubuntu.com/zesty/python3 >http://packages.ubuntu.com/zesty/python3.6 I posted about this on the ubuntu-devel mailing list: https://lists.ubuntu.com/archives/ubuntu-devel/2017-January/039648.html It's in the Zesty (and actually Yakkety) archives so that we can do the test rebuilds described in the above message. But it's not yet a "supported" version, which means that while most pure-Python third party modules should be importable, anything with an extension module will not be. On Debian and derivatives, we share what is essentially site-packages among all *installed* versions of Python 3, which doesn't necessarily mean that those packages will work, but they should be available on the import path with no extra work. Packages may still need to be functionally ported to Python 3.6 of course. However, because extension modules need to be recompiled by the Ubuntu build daemons, they only get done for "supported" versions. That term has a specific meaning in the Debian Python packaging sense, but I don't think the details are important (ask if you're interested). "Supported" is a step before "default", which is where we change the /usr/bin/python3 symlink. This step does not require an archive rebuild. Still for now you can `apt install python3.6` and run it via /usr/bin/python3.6 with the above caveats of course. It's functional enough to build venvs (you might want the python3.6-venv package), and tox will work, so it's everything folks should need to do porting work. Here's another page collecting some information: https://wiki.ubuntu.com/Python With a 9-12% build failure (again, forgetting about whether the packages actually work), it's enough that given where we are in the cycle, supporting Python 3.6 is not feasible. Debian Stretch just entered freeze so any work we do in Ubuntu to make packages Python 3.6 compatible will eventually have to be synced back to Debian, since they can't be uploaded there directly until Stretch is released. Zesty itself enters feature freeze on Feb 16, so that's another looming deadline on the amount of work we can accomplish this cycle. My plan is to enable Python 3.6 as a supported version early in the Zesty+1 cycle, hopefully before the first archive rebuild. I don't know whether Stretch will be released by then, but we'll deal with as we have before if that's the case. In the meantime, this should give upstreams a couple of more months to continue to port, and it will give us a full cycle to work on porting packages in Ubuntu. I plan for 18.04 LTS to ship only Python 3.6 (similarly for Debian Stretch+1). Dropping Python 3.5 does require an archive rebuild, but it's much less risky than adding a new version. The best way to help right now is to work with upstreams to port to Python 3.6 if necessary. You can see our test rebuild results here: https://launchpad.net/~pythoneers/+archive/ubuntu/python-rebuilds/+packages Anything with a red X means the package failed to build. That usually flexes at least the upstream's own unittests, but there may be deeper issues and other tests that fail, which may or may not hold up individual packages, and anything that depends on them. The Fedora/RH ecosystem probably has their own list, which I'd expect to mostly overlap with ours, but I don't have those links handy. Cheers, -Barry ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Mac OSX SSL certs
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 reads the readme during install. "I've installed python a thousand times before, I know what I'm doing." There are so many things that require SSL, and it's reasonably assumed to be functional by default. ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Mac OSX SSL certs
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 our bug tracker, http://bugs.python.org. -- Ned Deily [email protected] -- [] ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] GitHub migration scheduled for Friday
(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 patch author would appreciate it, but I don't think we need to require it as we have gone this long without it. > Currently, it requires some tricks to get these informations (the email is > partially hidden in the big tracker user list). Or are we moving slowly to > GitHub pull requests only? I hope we're moving quickly and not slowly. :) > Maybe the simplest option is to ask these informations to the author :-) I suspect if the patch author is still active you could ask them to make their patch into a PR and that will solve this problem. -Brett ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] GitHub migration scheduled for Friday
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 use the "author" and "committer" fields. If the author is set to the real author, the one who proposed the change on the bug tracker or someone else, we will be able to compute statistics on most active contributors to more easily detect them and promote them to core developers. What do you think? I agree that pull requests avoid the issues of filling manually the author field, but I expect that no everyone will use PR, especially because we will still use our current bug tracker which accepts to attach patch files. Ok to propose them to create a PR instead. Victor ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] GitHub migration scheduled for Friday
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 change on the bug tracker or someone > else, we will be able to compute statistics on most active > contributors to more easily detect them and promote them to core > developers. > > What do you think? I am +1 to this idea. The intention behind this idea is also good one. * When the patches come from Github PRs, the contribution authors are automatically tracked. The comitter would be merging the changes from the authors. * When contribution comes via Patches/ or for many existing patches, setting the author is a good idea. I have one question. If we disallow direct push to branches and the core-dev has to create a PR to merge the changes in, I guess it is still possible to have author information in the commit. ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
