Re: [python-committers] A different way to focus discussions
It seems like the PEP 572 discussions restarted on python-dev mailing
list with more than 100 emails in one week.
Stupid idea: we created a mailing list just to fix os.random(): PEP
522 and PEP 524, whereas these discussions were not the ones with the
most emails. Why not creating a new pep572 mailing list for the ones
who don't want to follow PEP 572 discussions?
A dedicated mailing list may help to discuss subtopics by opening new threads.
*Maybe* discussions would be more constructive on a dedicated mailing
list with less traffic and narrower audience?
Victor
2018-05-19 0:25 GMT+02:00 Guido van Rossum :
> Discussing PEPs on python-dev and python-ideas is clearly not scalable any
> more. (Even python-committers probably doesn't scale too well. :-)
>
> I wonder if it would make sense to require that for each PEP a new GitHub
> *repo* be created whose contents would just be a draft PEP and whose issue
> tracker and PR manager would be used to debate the PEP and propose specific
> changes.
>
> This way the discussion is still public: when the PEP-specific repo is
> created the author(s) can notify python-ideas, and when they are closer to
> submitting they can notify python-dev, but the discussion doesn't attract
> uninformed outsiders as much as python-{dev,ideas} discussions do, and it's
> much easier for outsiders who want to learn more about the proposal to find
> all relevant discussion.
>
> PEP authors may also choose to use a different repo hosting site, e.g.
> Bitbucket or GitLab. We can provide a script that allows checking the
> formatting of the PEP easily (basically pep2html.py from the peps repo).
>
> Using a separate repo per PEP has the advantage that people interested in a
> topic can subscribe to all traffic in that repo -- if we were to use the
> tracker of the peps repo you would have to subscribe to all peps traffic.
>
> Thoughts? (We can dogfood this proposal too, if there's interest. :-)
>
> --
> --Guido van Rossum (python.org/~guido)
>
> ___
> 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 mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] A different way to focus discussions
Le 28/06/2018 à 13:04, Victor Stinner a écrit : > It seems like the PEP 572 discussions restarted on python-dev mailing > list with more than 100 emails in one week. > > Stupid idea: we created a mailing list just to fix os.random(): PEP > 522 and PEP 524, whereas these discussions were not the ones with the > most emails. Why not creating a new pep572 mailing list for the ones > who don't want to follow PEP 572 discussions? PEP 572 is a language-wide change. Presumably those who don't want to follow discussions will still want to give their opinion (or informal vote) at the end. Which will give rise to other discussions... What strikes me is that we have such long-lasting and intense discussion about a feature which, whether approved or not, will not significantly change Python's popularity or appeal or ability to solve real-world problems. Perhaps this is a case where « Nature abhors a vacuum » : we're getting focussed on whatever comes up to fill the narrative of Python's evolution. 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/
[python-committers] Python 3.7.0 is now available! (and so is 3.6.6)
On behalf of the Python development community and the Python 3.7 release team, we are pleased to announce the availability of Python 3.7.0. Python 3.7.0 is the newest feature release of the Python language, and it contains many new features and optimizations. You can find Python 3.7.0 here: https://www.python.org/downloads/release/python-370/ Most third-party distributors of Python should be making 3.7.0 packages available soon. See the "What’s New In Python 3.7" document (https://docs.python.org/3.7/whatsnew/3.7.html) for more information about features included in the 3.7 series. Detailed information about the changes made in 3.7.0 can be found in its change log. Maintenance releases for the 3.7 series will follow at regular intervals starting in July of 2018. We hope you enjoy Python 3.7! P.S. We are also happy to announce the availability of Python 3.6.6, the next maintenance release of Python 3.6: https://www.python.org/downloads/release/python-366/ Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation. https://www.python.org/psf/ -- 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/
