On Sep 26, 2018, at 19:28, Mariatta Wijaya wrote:
>
> Really sorry folks, but I also would like to request an extension, by one
> week to Oct 8.
> It's not because I've been slacking; I've started a five-page document (only
> Barry has seen it), but I still need his help before it can be ready
Really sorry folks, but I also would like to request an extension, by one
week to Oct 8.
It's not because I've been slacking; I've started a five-page document
(only Barry has seen it), but I still need his help before it can be ready
for the public.
In addition, I'm facing personal health issue.
On Wed, Sep 26, 2018 at 1:25 PM Paul Moore wrote:
[..]
> but I don't know how
> useful it would be in practice - can you give some examples of use
> cases?)
It's hard to give a real life example as "py" doesn't support this,
but I can imagine the following scenario: if I have a script that uses
On Wed, 26 Sep 2018 at 18:15, Yury Selivanov wrote:
>
> On Wed, Sep 26, 2018 at 12:28 PM Brett Cannon wrote:
> [..]
> >> What is the status of Brett's UNIX Python launcher "py" by the way?
> >
> >
> > You can see the current TODO list at
> > https://crates.io/crates/python-launcher . Basically
On Tue, 25 Sep 2018 at 15:58, Victor Stinner wrote:
> Serhiy:
> > And changing the major version number itself is significant breaking
> change. From the name of the executable (python3 vs python4) hardcoded in
> Python
>
> IMHO It's time to discuss again modifying the "python" program to always
On 9/25/18 9:30 PM, Yury Selivanov wrote:
What's the current plan for what version of Python we release after 3.9?
The reason I'm asking this is because I frequently need to refer to
*that version* of Python in the documentation, especially when I'm
deprecating APIs or behavior. Right now I'm
For the record, Guido prefer 3.10 to 4.0, before he retired BDFL.
https://python.zulipchat.com/#narrow/stream/116503-core/subject/rhel/near/124934902
Regards,
--
INADA Naoki
___
python-committers mailing list
python-committers@python.org
Hi,
On 25/09/18 20:30, Yury Selivanov wrote:
What's the current plan for what version of Python we release after 3.9?
[snip]
For the record, we account for the following version tests when
analysing code (on lgtm.com):
sys.version == "3"
sys.version_info > (3,)
sys.version_info[0] == 3
Thanks, Steve, for writing this up:
https://www.python.org/dev/peps/pep-8013/
A couple of comments:
I like the council model, but don't understand why the core developers
should be stripped from any decision powers.
External people will not have the institutional knowledge core
developers
Could the authors of those PEPs please at least publish a rough
outline of what their model is all about ?
It doesn't help if we set a deadline only to find that we should
have written up a competing PEP shortly before the deadline
passes.
The only text we have at this point is PEP 8013:
I'm still optimistic that the October 1 deadline is achievable. It's important
for the larger Python community to have confidence that we enter 2019 with a
governance plan.
> On Sep 25, 2018, at 2:58 AM, Antoine Pitrou wrote:
>
>
> Le 24/09/2018 à 20:32, Mariatta Wijaya a écrit :
>> It is
11 matches
Mail list logo
