[python-committers] How does GitHub count contributors?
Hello, This is a bit of a futile question, but I realize I'm nowhere to be seen in https://github.com/python/cpython/graphs/contributors Is there some map file somewhere that I must update to match my commit e-mail to my GitHub account? Regards Antoine. ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] [Python-Dev] New workflow change: Welcome to blurb
On 06/23/2017 10:55 PM, Nick Coghlan wrote: Aye, towncrier and OpenStack's reno were the two main alternatives we looked at in addition to Larry's offer of creating a tool specifically for CPython: https://github.com/python/core-workflow/issues/6 Fun fact: all three tools started at about the same time, at least according to publicly visible commits. Towncrier started December 2015, reno in August 2015, and my first commits to "mergenews" (which eventually became blurb) were in September of 2015. We'd actually been discussing it on bpo since at least September 2013: https://bugs.python.org/issue18967 //arry/ ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] How does GitHub count contributors?
On 6/24/2017 11:05 AM, Antoine Pitrou wrote: Hello, This is a bit of a futile question, but I realize I'm nowhere to be seen in https://github.com/python/cpython/graphs/contributors Is there some map file somewhere that I must update to match my commit e-mail to my GitHub account? All I did was to a) create a github account and b) add the GitHub Name to my bpo profile page. You appear to have done the same. Brett Cannon 'added' coredevs to github.com/python, and you appear to have been included since you have already made github commits. I use the same email for both github and bpo. I can't see if your github email is the same as your primary bpo email and I don't know if that makes any difference. Brett Cannon is the most likely one to help you any further. tjr ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] How does GitHub count contributors?
Le 24/06/2017 à 18:05, Terry Reedy a écrit : > > I use the same > email for both github and bpo. I can't see if your github email is the > same as your primary bpo email and I don't know if that makes any > difference. I added a secondary e-mail to my GitHub account (matching the e-mail I used for most commits) and it seems to be much better now! Regards Antoine. ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] How does GitHub count contributors?
On Sat, 24 Jun 2017 at 09:22 Antoine Pitrou wrote: > > Le 24/06/2017 à 18:05, Terry Reedy a écrit : > > > > I use the same > > email for both github and bpo. I can't see if your github email is the > > same as your primary bpo email and I don't know if that makes any > > difference. > > I added a secondary e-mail to my GitHub account (matching the e-mail I > used for most commits) and it seems to be much better now! > Yep, just keep adding email addresses until you get all your commits. :) ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] How does GitHub count contributors?
> On Jun 24, 2017, at 11:05 AM, Antoine Pitrou wrote: > > > Hello, > > This is a bit of a futile question, but I realize I'm nowhere to be seen > in https://github.com/python/cpython/graphs/contributors > > Is there some map file somewhere that I must update to match my commit > e-mail to my GitHub account? That’s interesting, have you used multiple email addresses with the Python VCS history by any chance? If so you can add them all to your Github account and it should associate all of them with you. — Donald Stufft ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] New workflow change: Welcome to blurb
On 06/23/2017 11:25 PM, Serhiy Storchaka wrote: I have installed it, but how to use it? $ python3 -m pip install --user blurb Collecting blurb Using cached blurb-1.0-py3-none-any.whl Installing collected packages: blurb Successfully installed blurb-1.0 $ python3 -m blurb /usr/bin/python3: No module named blurb It's on your path. Just run % blurb from inside a CPython repo. I'm amazed that your first thought was "python -m blurb". //arry/ ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] New workflow change: Welcome to blurb
On 6/23/2017 11:24 PM, Larry Hastings wrote: > You can install blurb from pip: > > % pip3.6 install blurb This does not seem to work right. On Windows: C:\Users\Terry>py -3 -m pip install blurb Collecting blurb Downloading blurb-1.0-py3-none-any.whl Installing collected packages: blurb Successfully installed blurb-1.0 Explorer shows that 3.6 site-packages has a 'blurb-1.0.dist-info' directory but neither blurb.py nor 'blurb/' is present. So the following are to be expected. C:\Users\Terry>py -3 -m blurb C:\Programs\Python36\python.exe: No module named blurb > py -3 >>> import blurb ... ModuleNotFoundError: No module named 'blurb' Serhiy reported a similar problem on, I presume, some flavor of Linux. tjr ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] New workflow change: Welcome to blurb
On 06/24/2017 09:40 AM, Terry Reedy wrote: On 6/23/2017 11:24 PM, Larry Hastings wrote: > You can install blurb from pip: > > % pip3.6 install blurb This does not seem to work right. On Windows: C:\Users\Terry>py -3 -m pip install blurb Collecting blurb Downloading blurb-1.0-py3-none-any.whl Installing collected packages: blurb Successfully installed blurb-1.0 Explorer shows that 3.6 site-packages has a 'blurb-1.0.dist-info' directory but neither blurb.py nor 'blurb/' is present. So the following are to be expected. C:\Users\Terry>py -3 -m blurb C:\Programs\Python36\python.exe: No module named blurb > py -3 >>> import blurb ... ModuleNotFoundError: No module named 'blurb' Serhiy reported a similar problem on, I presume, some flavor of Linux. I replied to Serhiy; it's just "blurb", it's a command-line tool, it's not a package or a module. It should be a command on your path. TBH I don't know if installation of a command-line tool like that works on Windows. The tool itself was ported to Windows by Zach at the PyCon core dev sprints last month, though that predates the PyPI work, and in any case I could have broken the Windows support since then. Unfortunately I'm no longer a qualified Windows developer, so if it doesn't work on Windows I fear someone will have to send me a PR. //arry/ ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] [Python-Dev] New workflow change: Welcome to blurb
On Sat, 24 Jun 2017 at 09:46 Larry Hastings wrote: > On 06/24/2017 09:40 AM, Terry Reedy wrote: > > On 6/23/2017 11:24 PM, Larry Hastings wrote: > > > You can install blurb from pip: > > > > % pip3.6 install blurb > > This does not seem to work right. On Windows: > > C:\Users\Terry>py -3 -m pip install blurb > Collecting blurb > Downloading blurb-1.0-py3-none-any.whl > Installing collected packages: blurb > Successfully installed blurb-1.0 > > Explorer shows that 3.6 site-packages has a 'blurb-1.0.dist-info' > directory but neither blurb.py nor 'blurb/' is present. So the following > are to be expected. > > C:\Users\Terry>py -3 -m blurb > C:\Programs\Python36\python.exe: No module named blurb > > > py -3 > >>> import blurb > ... > ModuleNotFoundError: No module named 'blurb' > > Serhiy reported a similar problem on, I presume, some flavor of Linux. > > > I replied to Serhiy; it's just "blurb", it's a command-line tool, it's not > a package or a module. It should be a command on your path. > > TBH I don't know if installation of a command-line tool like that works on > Windows. The tool itself was ported to Windows by Zach at the PyCon core > dev sprints last month, though that predates the PyPI work, and in any case > I could have broken the Windows support since then. Unfortunately I'm no > longer a qualified Windows developer, so if it doesn't work on Windows I > fear someone will have to send me a PR. > One of the great perks of `python3 -m blurb` is it avoids needing to care about your PATH on any platform. Anyway, the next release of blurb -- whether that's 1.0.0.post1 or a bigger release -- will have a blurb.py as well as the entry point giving people the `blurb` command. And people can also use pipsi if they want to install blurb as more of a self-contained command-line app (at least on UNIX; don't know about its support on Windows). ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] [Python-Dev] New workflow change: Welcome to blurb
I just pushed blurb 1.0.0.post1 which re-packages everything using flit so there's a blurb.py and an entry point for the `blurb` command. That should meet everyone's needs for launching the tool. On Sat, 24 Jun 2017 at 09:54 Brett Cannon wrote: > On Sat, 24 Jun 2017 at 09:46 Larry Hastings wrote: > >> On 06/24/2017 09:40 AM, Terry Reedy wrote: >> >> On 6/23/2017 11:24 PM, Larry Hastings wrote: >> >> > You can install blurb from pip: >> > >> > % pip3.6 install blurb >> >> This does not seem to work right. On Windows: >> >> C:\Users\Terry>py -3 -m pip install blurb >> Collecting blurb >> Downloading blurb-1.0-py3-none-any.whl >> Installing collected packages: blurb >> Successfully installed blurb-1.0 >> >> Explorer shows that 3.6 site-packages has a 'blurb-1.0.dist-info' >> directory but neither blurb.py nor 'blurb/' is present. So the following >> are to be expected. >> >> C:\Users\Terry>py -3 -m blurb >> C:\Programs\Python36\python.exe: No module named blurb >> >> > py -3 >> >>> import blurb >> ... >> ModuleNotFoundError: No module named 'blurb' >> >> Serhiy reported a similar problem on, I presume, some flavor of Linux. >> >> >> I replied to Serhiy; it's just "blurb", it's a command-line tool, it's >> not a package or a module. It should be a command on your path. >> >> TBH I don't know if installation of a command-line tool like that works >> on Windows. The tool itself was ported to Windows by Zach at the PyCon >> core dev sprints last month, though that predates the PyPI work, and in any >> case I could have broken the Windows support since then. Unfortunately I'm >> no longer a qualified Windows developer, so if it doesn't work on Windows I >> fear someone will have to send me a PR. >> > > One of the great perks of `python3 -m blurb` is it avoids needing to care > about your PATH on any platform. > > Anyway, the next release of blurb -- whether that's 1.0.0.post1 or a > bigger release -- will have a blurb.py as well as the entry point giving > people the `blurb` command. And people can also use pipsi if they want to > install blurb as more of a self-contained command-line app (at least on > UNIX; don't know about its support on Windows). > ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] New workflow change: Welcome to blurb
On 6/24/2017 12:45 PM, Larry Hastings wrote: On 06/24/2017 09:40 AM, Terry Reedy wrote: On 6/23/2017 11:24 PM, Larry Hastings wrote: > You can install blurb from pip: > > % pip3.6 install blurb This does not seem to work right. On Windows: C:\Users\Terry>py -3 -m pip install blurb Collecting blurb Downloading blurb-1.0-py3-none-any.whl Installing collected packages: blurb Successfully installed blurb-1.0 Explorer shows that 3.6 site-packages has a 'blurb-1.0.dist-info' directory but neither blurb.py nor 'blurb/' is present. So the following are to be expected. C:\Users\Terry>py -3 -m blurb C:\Programs\Python36\python.exe: No module named blurb > py -3 >>> import blurb ... ModuleNotFoundError: No module named 'blurb' Serhiy reported a similar problem on, I presume, some flavor of Linux. I replied to Serhiy; it's just "blurb", it's a command-line tool, it's not a package or a module. It should be a command on your path. The reason I tried " -m blurb" is because that is the standard and recommended way to run installed scripts on Windows. That is how I run pip and cherry_picker, for instance. I found 'blurb' in <36dir>/Scripts/. The name and location are errors. 1. On Windows, python files need the .py extension. 2. That directory is not currently on the path on my machine. I believe it once was, but installing 3.5.3 replaced it with the 3.5 /Scripts. On Windows, 3rd party installers must not presume that any /Scripts directory is on the path. By default, none are. Solution: name the file blurb.py and put it in site-packages. This is standard and what is done by all other pip-installs that I have run. Put a copy in /Scripts if you want, but that is really optional and only sometimes effective. TBH I don't know if installation of a command-line tool like that works on Windows. The tool itself was ported to Windows by Zach at the PyCon core dev sprints last month, though that predates the PyPI work, and in any case I could have broken the Windows support since then. Unfortunately I'm no longer a qualified Windows developer, so if it doesn't work on Windows I fear someone will have to send me a PR. I only know what the end result should be. Pip-installed Cherry_picker works on Windows, so copy from the spec files for that, or ask whoever wrote the pip-upload. ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] New workflow change: Welcome to blurb
On 06/24/2017 10:30 AM, Terry Reedy wrote: Solution: name the file blurb.py and put it in site-packages. This is standard and what is done by all other pip-installs that I have run. Put a copy in /Scripts if you want, but that is really optional and only sometimes effective. Brett redid the installer with "flit" and pushed, and he says you should now be able to run blurb via "python3 -m blurb". Please update blurb (via pip3.6) and let us know if it now works for you on Windows. Cheers, //arry/ ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Travis now checks for whitespace issues in PRs
I just pushed a change to master, 3.6, and 3.5 where Tools/scripts/patchcheck.py now has a --travis option which will run the whitespace fixers from `make patchcheck` but trigger a Travis build failure if any changes were necessary. This only runs on Linux so it is a PR blocker, but also so it isn't done more than once per PR. This was not backported to 2.7 because I honestly didn't want to do the work to fix the merge conflicts. ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
