[python-committers] Steering Council Update for July 2019

2019-07-08 Thread Carol Willing 
I've posted an update from the Steering Council to our repo:

https://github.com/python/steering-council/blob/master/updates/2019-07-08_steering-council

I will also link to this on python-dev and on Discourse (discuss.python.org ).


For completeness, below is the full text.


# Steering Council Update


## Date: 2019-07-08

Steering Council updates will be posted irregularly and as needed.
We provide these updates to foster open and transparent communication about
Steering Council activity. We strive to post at least once every month.


# Message from the Steering Council

Sorry we've been silent for a while! With PyCon in Cleveland, the Language
Summit, Sprints, PEP activity, and a Python 3.8 beta release, it's been a busy
and productive May and June. Thank you all for your contributions. Below are
some of the outcomes of our weekly Steering Council conversations.

---

## Mandate

This section organizes Steering Council (SC) activity and projects
using the mandates listed in PEP 13.


### Language

> Maintain the quality and stability of the Python language and CPython 
> interpreter

- Inspired by Russell Keith-Magee's PyCon keynote about Black Swan events, the
  Steering Council is looking at what may impact Python for the next
  decade. We have been discussing this within the Steering Council and writing
  up some thoughts on major challenges facing Python. We'll continue to edit
  and polish this vision document and share it when we are ready for wider 
comment.


### Contributors

> Make contributing as accessible, inclusive, and sustainable as possible

- **Communications channels:** We are very pleased with the move of
  python-dev, etc. to Mailman 3. We now have a modern UI and easy search across
  mailing lists.

  Just a reminder to recap where announcements and conversations are taking 
place:

  - To reach core committers specifically, we will use
[email protected].

  - To reach the entire Python developer community, we will use
[email protected].

  - For specific requests to the SC (e.g., PEP reviews), please use
our public GitHub tracker at 
https://github.com/python/steering-council/issues.

  - To reach just the SC, you can email us at
[email protected].

  - We will also occasionally use Discourse, at
https://discuss.python.org (for example, Discourse is useful for
polls and votes).


### PEPs

> Establish appropriate decision-making processes for PEPs

- To request a PEP review, please file an issue on the
  [SC issue tracker](https://github.com/python/steering-council/issues).

PEP highlights include:

- PEP 570, "Python Positional-Only Parameters", by Larry Hastings, Pablo
  Galindo and others. *Appointed Guido van Rossum as BD.* "Completed."
- PEP 574, "Pickle protocol 5 with out-of-band data", Antoine Pitrou.
  *Appointed Nick Coghlan as BD.* "Marked Final."
- PEPs 576, 579, 580, 590 (competing PEPs on C function call optimizations by
  Mark Shannon and Jeroen Demeyer; note that PEP 576 is withdrawn in favor of
  PEP 590). *Appointed Petr Viktorin as BD.* "Accepted 590."
- PEP 578, "Python Runtime Audit Hooks", Steve Dower.
  *Appointed Christian Heimes as BD.* "Landed, about to be marked Final."


### Interaction with PSF

> Formalize and maintain the relationship between the core team and the PSF

- We began discussions about fundraising ideas for CPython projects and 
administrative support.

- A [donation 
page]([https://www.python.org/psf/donations/python-dev/](https://www.python.org/psf/donations/python-dev/))
 was created by the PSF and was linked from the
 [CPython 
repo]([https://github.com/python/cpython](https://github.com/python/cpython)). 
Any funds that are donated will be used for Core Developers to attend the core 
development sprints (to start; future possibilities are dependent on the amount 
of funds gathered).

- At the Steering Council's recommendation, the PSF also is looking at hiring a 
Project Manager to manage communication and
  some logistics for the 2020 Python 2.7 End of Life.

- The PSF Code of Conduct Workgroup is working on a revision of the CoC and
  its approval by the PSF board. Brett and Carol serve on the Workgroup.


### Governance

> Seek consensus among contributors and the core team before acting in a formal 
> capacity,

> Act as a "court of final appeal" for decisions where all other methods have 
> failed.

- The weekly SC meeting cadence (Tuesdays 3-4pm US West Coast time) has been
  working out well.

---


## Reference

This reference section summarizes the Steering Council's mandate and powers.


### Mandate (PEP 13)

The steering council shall work to:

- Maintain the quality and stability of the Python language and
  CPython interpreter,
- Make contributing as accessible, inclusive, and sustainable as
  possible,
- Formalize and maintain the relationship between the core team and
  the PSF,
- Establish appropriate decision-making processes for PEPs,
- Seek consensus among contribu

[python-committers] Re: Steering Council Update for July 2019

2019-07-08 Thread Carol Willing 
Sorry for the incorrect link. Here is the corrected link:

https://github.com/python/steering-council/blob/master/updates/2019-07-08_steering-council-update.md

On Mon, Jul 8, 2019, at 7:16 AM, Carol Willing wrote:
> I've posted an update from the Steering Council to our repo:

> https://github.com/python/steering-council/blob/master/updates/2019-07-08_steering-council
> 
> I will also link to this on python-dev and on Discourse (discuss.python.org ).

> 
> For completeness, below is the full text.
> 
> 
> # Steering Council Update


## Date: 2019-07-08

Steering Council updates will be posted irregularly and as needed.
We provide these updates to foster open and transparent communication about
Steering Council activity. We strive to post at least once every month.


# Message from the Steering Council

Sorry we've been silent for a while! With PyCon in Cleveland, the Language
Summit, Sprints, PEP activity, and a Python 3.8 beta release, it's been a busy
and productive May and June. Thank you all for your contributions. Below are
some of the outcomes of our weekly Steering Council conversations.

---

## Mandate

This section organizes Steering Council (SC) activity and projects
using the mandates listed in PEP 13.


### Language

> Maintain the quality and stability of the Python language and CPython 
> interpreter

- Inspired by Russell Keith-Magee's PyCon keynote about Black Swan events, the
  Steering Council is looking at what may impact Python for the next
  decade. We have been discussing this within the Steering Council and writing
  up some thoughts on major challenges facing Python. We'll continue to edit
  and polish this vision document and share it when we are ready for wider 
comment.


### Contributors

> Make contributing as accessible, inclusive, and sustainable as possible

- **Communications channels:** We are very pleased with the move of
  python-dev, etc. to Mailman 3. We now have a modern UI and easy search across
  mailing lists.

  Just a reminder to recap where announcements and conversations are taking 
place:

  - To reach core committers specifically, we will use
[email protected].

  - To reach the entire Python developer community, we will use
[email protected].

  - For specific requests to the SC (e.g., PEP reviews), please use
our public GitHub tracker at 
https://github.com/python/steering-council/issues.

  - To reach just the SC, you can email us at
[email protected].

  - We will also occasionally use Discourse, at
https://discuss.python.org (for example, Discourse is useful for
polls and votes).


### PEPs

> Establish appropriate decision-making processes for PEPs

- To request a PEP review, please file an issue on the
  [SC issue tracker](https://github.com/python/steering-council/issues).

PEP highlights include:

- PEP 570, "Python Positional-Only Parameters", by Larry Hastings, Pablo
  Galindo and others. *Appointed Guido van Rossum as BD.* "Completed."
- PEP 574, "Pickle protocol 5 with out-of-band data", Antoine Pitrou.
  *Appointed Nick Coghlan as BD.* "Marked Final."
- PEPs 576, 579, 580, 590 (competing PEPs on C function call optimizations by
  Mark Shannon and Jeroen Demeyer; note that PEP 576 is withdrawn in favor of
  PEP 590). *Appointed Petr Viktorin as BD.* "Accepted 590."
- PEP 578, "Python Runtime Audit Hooks", Steve Dower.
  *Appointed Christian Heimes as BD.* "Landed, about to be marked Final."


### Interaction with PSF

> Formalize and maintain the relationship between the core team and the PSF

- We began discussions about fundraising ideas for CPython projects and 
administrative support.

- A [donation 
page]([https://www.python.org/psf/donations/python-dev/](https://www.python.org/psf/donations/python-dev/))
 was created by the PSF and was linked from the
 [CPython 
repo]([https://github.com/python/cpython](https://github.com/python/cpython)). 
Any funds that are donated will be used for Core Developers to attend the core 
development sprints (to start; future possibilities are dependent on the amount 
of funds gathered).

- At the Steering Council's recommendation, the PSF also is looking at hiring a 
Project Manager to manage communication and
  some logistics for the 2020 Python 2.7 End of Life.

- The PSF Code of Conduct Workgroup is working on a revision of the CoC and
  its approval by the PSF board. Brett and Carol serve on the Workgroup.


### Governance

> Seek consensus among contributors and the core team before acting in a formal 
> capacity,

> Act as a "court of final appeal" for decisions where all other methods have 
> failed.

- The weekly SC meeting cadence (Tuesdays 3-4pm US West Coast time) has been
  working out well.

---


## Reference

This reference section summarizes the Steering Council's mandate and powers.


### Mandate (PEP 13)

The steering council shall work to:

- Maintain the quality and stability of the Python language and
  CPython interpreter,
- Make contrib

[python-committers] Re: [RELEASE] Python 3.8.0b2 is now available for testing

2019-07-08 Thread Barry Warsaw 
I’ve updated the official images to include 3.8.0b2:

https://gitlab.com/python-devs/ci-images/tree/master

Cheers,
-Barry

> On Jul 4, 2019, at 15:05, Łukasz Langa  wrote:
> 
> Signed PGP part
> After a few days of delay, but somewhat cutely timed with the US Independence 
> Day, I present you Python 3.8.0b2:
> 
> https://www.python.org/downloads/release/python-380b2/ 
> 
> 
> This release is the second of four planned beta release previews. Beta 
> release previews are intended to give the wider community the opportunity to 
> test new features and bug fixes and to prepare their projects to support the 
> new feature release. The next pre-release of Python 3.8 will be 3.8.0b3, 
> currently scheduled for 2019-07-29.
> 
> Call to action
> 
> We strongly encourage maintainers of third-party Python projects to test with 
> 3.8 during the beta phase and report issues found to the Python bug tracker 
>  as soon as possible. While the release is planned 
> to be feature complete entering the beta phase, it is possible that features 
> may be modified or, in rare cases, deleted up until the start of the release 
> candidate phase (2019-09-30). Our goal is have no ABI changes after beta 3 
> and no code changes after 3.8.0rc1, the release candidate. To achieve that, 
> it will be extremely important to get as much exposure for 3.8 as possible 
> during the beta phase.
> 
> Please keep in mind that this is a preview release and its use is not 
> recommended for production environments.
> 
> No more non-bugfixes allowed on the “3.8” branch
> 
> The time has come, team. Please help make Python 3.8 as stable as possible 
> and keep all features not currently landed for Python 3.9. Don’t fret, it’ll 
> come faster than you think.
> 
> 
> - Ł
> 
> 



signature.asc
Description: Message signed with OpenPGP
___
python-committers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/JRX5LSDAUVU6JELT26WACVNGVDSIGZNK/
Code of Conduct: https://www.python.org/psf/codeofconduct/