[python-committers] The PSF's new Code of Conduct and how it applies to Python's development
[this is being emailed out to python-committer and python-dev separately, so apologies for those who get a duplicate email] The steering council wanted to let everyone know that the PSF released a new Code of Conduct which was announced at https://pyfound.blogspot.com/2019/09/the-python-software-foundation-has_24.html and that it applies to Python's development. Specifically, this new Code of Conduct lists Python's development spaces and those participating in those spaces as being under the CoC (we were implicitly under the old CoC on PSF-sponsored and run infrastructure, but now it's explicitly called out). So that means python-committers, python-dev, python-ideas, everything on GitHub, discuss.python.org, core dev sprints, PSF-sponsored conferences, etc. all fall under this CoC. The steering council wanted to make sure people were aware of this new Code of Conduct so no one was caught off-guard and to make sure people were aware that it did apply to all of us. The steering council also supports this Code of Conduct. One other thing the steering council wanted to point out is that we believe CoC violations should be reported directly to the Conduct WG as outlined at https://www.python.org/psf/conduct/reporting/. The thinking is that since we all know each other on the development team there's a good chance of a conflict of interest if reports were to go to the steering council, and so it's simpler to just advise people go straight to the Conduct WG (Carol and I will recuse ourselves as appropriate since we are both on the Conduct WG). I will also say that people have come to me personally in the past and asked if something was a CoC violation, and going forward my answer will be "report it to the Conduct WG and let them make that decision". Same goes for incidents where people believe something is a CoC violation and they want to report it to someone: let the Conduct WG know (which I have already started telling people who come to me with CoC concerns). ___ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/6QIMLZ65D2HVBRGXRMOF2KOLFRXH4IRG/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: PEP 581/588 RFC: Collecting feedback about GitHub Issues
Sorry, but please leave comments in the GitHub issue, one feature request per comment. This will allow people to give +1 reaction to your request https://github.com/python/core-workflow/issues/359 On Thu, Sep 12, 2019, 2:30 AM Steve Dower wrote: > On 11Sep2019 1117, Steven D'Aprano wrote: > > On Wed, Sep 11, 2019 at 10:17:48AM +0100, Benjamin Peterson wrote: > >> In other words, vanilla GitHub issue search does address Raymond's > request? > > > > Given that github search is unlikely to be able to search "our > > voluminous history of already evaluated and decided feature requests" on > > b.p.o then it probably doesn't. > > > > Besides, I spent about two minutes playing with github's filter/search, > > not long enough to really test its capabilities and limitations. > > > > I've spent a couple of years playing with GitHub's filter/search on much > smaller projects than CPython and I find its search woefully inadequate > compared to bpo. > > But I know some people find it easier, so I'll probably rely on them to > do the history searches for me after we switch. > > Cheers, > Steve > ___ > python-committers mailing list -- python-committers@python.org > To unsubscribe send an email to python-committers-le...@python.org > https://mail.python.org/mailman3/lists/python-committers.python.org/ > Message archived at > https://mail.python.org/archives/list/python-committers@python.org/message/ZQTBEO26FJPJNWXSYTJPIKHYPZBPHJFD/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/F2NYJRIL7LITL2ENO7OK6CVPKDSB6J36/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] [RELEASE] Python 3.7.5rc1 is now available for testing
Python 3.7.5rc1 is now available for testing. 3.7.5rc1 is the release preview of the next maintenance release of Python 3.7, the latest feature release of Python. Assuming no critical problems are found prior to 2019-10-14, no code changes are planned between now and the final release. This release candidate is intended to give you the opportunity to test the new security and bug fixes in 3.7.5. We strongly encourage you to test your projects and report issues found to bugs.python.org as soon as possible. Please keep in mind that this is a preview release and, thus, its use is not recommended for production environments. You can find the release files, a link to the changelog, and more information here: https://www.python.org/downloads/release/python-375rc1/ -- Ned Deily n...@python.org -- [] ___ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/JE56V6R6LJPCHOVX5BW7QOLJXA6GEQ73/ Code of Conduct: https://www.python.org/psf/codeofconduct/
