Re: [python-committers] 2019 Steering Council Nominations Closure
Nominations are final and the ballot has been frozen in Helios based on the status of PEP 8100 at https://github.com/python/peps/blob/3d675543af3db6bf07d26f37f77599d10b60e5dd/pep-8100.rst#candidates. Voting will open at 12:00 UTC 2019-01-21 (In about 3 hours). Voters will receive an email based on the contents of the voter roll at https://github.com/python/voters/blob/master/2019-01-21-2019-python-steering-council-election.csv when the election opens.___ 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] 2019 Steering Council Election Voting
Ballots have been distributed per PEP 8100 and voting is open. This election is scheduled to end at Feb. 4, 2019, noon (UTC). If you expected to receive a ballot but did not, please contact me at [email protected].___ 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] "bedevere/news — News entry file name incorrectly formatted"
Hello, The NEWS file check failed in a weird way here: https://github.com/python/cpython/pull/11531 Could someone take a look and find out the reason for failure? Thanks 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] "bedevere/news — News entry file name incorrectly formatted"
On Jan 21, 2019, at 14:44, Antoine Pitrou wrote: > The NEWS file check failed in a weird way here: > https://github.com/python/cpython/pull/11531 > > Could someone take a look and find out the reason for failure? I'm mystified. The blurb news file in the PR looks fine and produces a valid changelog with a local docs build. I don't see anything odd on the GitHub end of things. Perhaps Mariatta can take a look at the Bevedere end? -- Ned Deily [email protected] -- [] ___ 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] "bedevere/news — News entry file name incorrectly formatted"
A potential explanation: the original PR title was formatted as "bpo-XX : ..." (note the space before the colon). I fixed it to "bpo-X: ..." but the bot didn't run again. Perhaps that's related? Le 21/01/2019 à 21:05, Ned Deily a écrit : > On Jan 21, 2019, at 14:44, Antoine Pitrou wrote: >> The NEWS file check failed in a weird way here: >> https://github.com/python/cpython/pull/11531 >> >> Could someone take a look and find out the reason for failure? > > I'm mystified. The blurb news file in the PR looks fine and produces a valid > changelog with a local docs build. I don't see anything odd on the GitHub > end of things. Perhaps Mariatta can take a look at the Bevedere end? > > -- > Ned Deily > [email protected] -- [] > ___ 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] "bedevere/news — News entry file name incorrectly formatted"
On Jan 21, 2019, at 15:07, Antoine Pitrou wrote: > A potential explanation: the original PR title was formatted as > "bpo-XX : ..." (note the space before the colon). I fixed it to > "bpo-X: ..." but the bot didn't run again. Perhaps that's related? Possibly, if you modified the news entry while the other CI checks were still running? I guess you could force the whole CI process to run again by closing and re-opening the PR. Or a release manager could override it with an appropriate bribe. -- Ned Deily [email protected] -- [] ___ 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] "bedevere/news — News entry file name incorrectly formatted"
Le 21/01/2019 à 21:11, Ned Deily a écrit : > On Jan 21, 2019, at 15:07, Antoine Pitrou wrote: >> A potential explanation: the original PR title was formatted as >> "bpo-XX : ..." (note the space before the colon). I fixed it to >> "bpo-X: ..." but the bot didn't run again. Perhaps that's related? > > Possibly, if you modified the news entry while the other CI checks were still > running? I guess you could force the whole CI process to run again by > closing and re-opening the PR. Or a release manager could override it with > an appropriate bribe. Right, I forced the CI checks and things seem fine now. Thank you! Antoine. ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
