Recently I received 20 one-year licenses from JetBrains for the PyCharm IDE (Professional) and other JetBrains products (the licenses cover their "All Products Pack") for use in Python development. There are 11 licenses available - of the licenses I asked for last year, nine people took them up, so those are in use and come out of the allocation of 20.
Those of you who took up the licences last time should find that the tools continue to work normally. The licences expire on 27 November 2018.
If any others of you are interested in using these licenses, let me know off-list and I will forward the license access details to you. To access the licenses, you will need to have (or create) a JetBrains account.
A couple days ago Nathaniel pushed significant changes to his governance
PEP (PEP 8016). This means some governance PEPs are apparently still
*not* finalized. This raises a problem: when can we consider that we
are reading the final version of a proposal (barring wording fixes or
improvements), not some work in progress draft?
Not everyone keeps an eye daily on PEP changes and discussions. It
would be nice to be able to make one's mind at an idle pace. But that
requires that PEP authors don't make last-minute changes in an attempt
to gather more support.
In my vote, I may have to devaluate those proposals that keep changing
in the last days before the vote, because it doesn't sound like the
author can be trusted to propose a stable model.
As a reminder, PEP 8001 states:
"November 16th, 2018 to November 30th, 2018 is the official governance PEP
review period. We discourage the PEP authors from making major substantive
changes during this period, although it is expected that minor tweaks may
occur, as the result of this discussion period."
Looking at the commit history, the last change to PEP 8016 was on Nov 15 my
timezone, and I'm assuming it was Nov 15 in PEP 8016 authors' timezone too,
so I think it was still allowed. There shouldn't be any more major changes
going forward though.
I would suggest that PEP 8001 can also say that once voting start (Dec 1),
PEPs 801x should be locked and not editable anymore.
On Sun, Nov 18, 2018, 3:17 AM Antoine Pitrou <antoine(a)python.org wrote:
> Hello folks,
> A couple days ago Nathaniel pushed significant changes to his governance
> PEP (PEP 8016). This means some governance PEPs are apparently still
> *not* finalized. This raises a problem: when can we consider that we
> are reading the final version of a proposal (barring wording fixes or
> improvements), not some work in progress draft?
> Not everyone keeps an eye daily on PEP changes and discussions. It
> would be nice to be able to make one's mind at an idle pace. But that
> requires that PEP authors don't make last-minute changes in an attempt
> to gather more support.
> In my vote, I may have to devaluate those proposals that keep changing
> in the last days before the vote, because it doesn't sound like the
> author can be trusted to propose a stable model.
> python-committers mailing list
> Code of Conduct: https://www.python.org/psf/codeofconduct/
Thank you to everybody who voiced concern that the originally planned voting schedule of Nov 16 - Nov 30 was rushed. In the interest of ensuring everybody feels included, as well as to allow time for PEP 801x review and clarifications, Barry Warsaw and the other PEP 801x authors _ decided to move the vote by two weeks. Barry opened a PR _ which I just merged.
Summary of changes:
- starting tomorrow until December 1st we are entering an official PEP 801x review period. Substantive changes to those PEPs are discouraged, clarifications as the result of the discussion are encouraged.
- the actual vote will happen on CIVS between December 1st and December 16th.
All details are in PEP 8001 which has been now Accepted and will be marked Final sometime later this week after the dust settles. Please read it carefully.
We are sorry for the late change and any inconvenience this might have caused you. Our foremost concern is to ensure the vote is going to be considered fair, inclusive and legitimate. We hope adjusting the timing helps with that.
One last thing. During the discussion phase, please try to keep discussions on Discourse where they were held until this point. Moderators will be available in this period to help with readability.
..  Well, we couldn't reach Steve who is in Scotland and Jack. We are sorry we couldn't wait for your opinions but the pressure of time didn't allow us to do so.
..  https://github.com/python/peps/pull/841/
According to the PEP 8001: "The vote will happen in a 2-week-long
window from November 16 2018 to November 30 (Anywhere-on-Earth)." It's
now in less than two weeks.
I see that the PEP 8001 is still being updated (voting method). Should
we still expect new changes before the vote starts? Can we set a
deadline, like November 15 (Anywhere-on-Earth)?
Nathaniel Smith and Donald Stuff have a draft PEP 8016 which is still
at the "ideas" stage:
What is the deadline to submit new governance PEP and to update
governance PEPs? November 15 (Anywhere-on-Earth)?
For the PEP 8001, who is going to organize the vote? It seems like
there isn't much to do. The bare minimum is just to create the private
repository. Or is it already created?
Another task would be to send notices about the vote on all
communication channels used by core developers? Announce 1 week before
it starts, when it starts, and maybe also remainder 3 days and 1 day
before it ends?
Does someone plan to have holiday during the vote and will not be able to vote?
Which tool can be used to compute the vote result? Parse the text
files in the Git repository and implement the Condorcet method.
There's been a lot of clarification and critique for individual
governance proposals, but not a lot of discussion of how they compare
to each other or what different core devs think is important. And I
know that for complicated issues like this, I often don't understand
the trade-offs until I talk them over with other people, so I'm pretty
nervous about voting without having that discussion!
I started a poll on the discourse to get a sense of what people are
thinking, and talk it through. Please join us!
Nathaniel J. Smith -- https://vorpus.org