Chris Barker via Python-ideas writes:
> On Fri, Sep 21, 2018 at 1:24 PM James Lu wrote:
>
> > One of the reasons Guido left was the insane volume of emails he
> > had to read on Python-ideas.
>
> You'd have to ask Guido directly, but I don't think so. It wasn't
> the volume, but the natur
Executive summary: Writing a PEP is an inherently uncertain process.
Achieving "community consensus" is the goal of the process, not a
precondition.
Anders Hovmöller writes:
> In general pep1 is frustratingly vague. Terms like “community
> consensus” without defining community or what number
Michael Selik writes:
> On Thu, Sep 20, 2018 at 2:13 AM Stephen J. Turnbull
> wrote:
> > That's because completion of discussion has never been a requirement
> > for writing a PEP.
>
> Not for drafting, but for submitting. For my own PEP submission, I
> received the specific feedback that
Hi,
I implemented a sphinx extension to include contracts in the documentation:
https://github.com/Parquery/sphinx-icontract
The extension supports inheritance. It lists all the postconditions and
invariants including the inherited one. The preconditions are grouped by
classes with ":requires:" an
Process suggestions that could minimize non-BDFL's BDFL legwork:
* https://github.com/python/peps
* https://github.com/pypa/interoperability-peps
* Use GitHub reactions for voting on BDFL delegates, PEP final approval,
and PEP sub issues?
* Specify a voting deadline?
* How to make a quorum ca
> If one doesn't know who the senior developers are yet, she should think
> twice about whether she's ready to PEP anything. That's not a litmus
> test; some PEPs have eventually succeeded though the proponent was new
> to the project development process.[2] But it's a lot less painful if
> you
On Saturday, September 22, 2018, Wes Turner wrote:
>
> It seems like everything's fine, but I would have no idea, BTW
>
Would project boards be helpful for coordinating proposal status
information, or extra process for something that's already working just
fine?
https://github.com/python/peps/p
Here are links to the Apache governance docs:
https://www.apache.org/foundation/governance/#technical
https://www.apache.org/foundation/governance/pmcs.html
Which are the PSF docs for these exact same processes for open source
governance? (In re: to transitioning from BDFL is not dead, but)
htt
Could I get some feedback on this? I'd like to know if anyone thinks it
might make it through the pep process before spending too much (more) time
on it. That said, it seems valuable to me, and I'm willing to put in the
time, of course, IF it has a chance.
---
Problem:
On Sat, 22 Sep 2018 at 10:56, Anders Hovmöller wrote:
>
>
>
> > If one doesn't know who the senior developers are yet, she should think
> > twice about whether she's ready to PEP anything. That's not a litmus
> > test; some PEPs have eventually succeeded though the proponent was new
> > to the pr
Sorry, hit send too soon...
On Sat, 22 Sep 2018 at 13:24, Paul Moore wrote:
>
>
> On Sat, 22 Sep 2018 at 10:56, Anders Hovmöller wrote:
> >
> >
> >
> > > If one doesn't know who the senior developers are yet, she should think
> > > twice about whether she's ready to PEP anything. That's not a l
On Saturday, September 22, 2018, Lee Braiden wrote:
>
> Proposal:
>
> The addition of a ?= operator could provide an elegant solution:
>
> > def teleport(from, to, hitchiker=None, food_accessory=None,
> comfort_accessory=None):
> > hitchhiker ?= Fly()
> > food_
On Sat, 22 Sep 2018 at 12:54, Lee Braiden wrote:
>
> Could I get some feedback on this? I'd like to know if anyone thinks it
> might make it through the pep process before spending too much (more) time on
> it. That said, it seems valuable to me, and I'm willing to put in the time,
> of cours
That's an idea that could be added to my thread "dialects of python" in
order to compile some fancy or specific syntax to regular python.
Le sam. 22 sept. 2018 à 13:53, Lee Braiden a écrit :
> Could I get some feedback on this? I'd like to know if anyone thinks it
> might make it through the pe
>>>
>>> I think that entire paragraph made it sound even worse than what I wrote
>>> originally. It reads to an outsider as “if you don’t know what’s wrong I’m
>>> not going to tell you”.
>
> More like, if you're not sufficiently familiar with the community or
> the language,
And now you mad
> If Python were going to address this problem, I think it better to do
> something like:
>
> def teleport(from, to, hitchiker => Fly(), accessory =>
> Towel(hitchhiker)):
> etc.
>
> Where => specifies an expression thst is evaluated inside the function and Is
> approx
On Sat, Sep 22, 2018 at 5:53 AM Anders Hovmöller
wrote:
>
>
> >>>
> >>> I think that entire paragraph made it sound even worse than what I
> wrote originally. It reads to an outsider as “if you don’t know what’s
> wrong I’m not going to tell you”.
> >
> > More like, if you're not sufficiently fam
On Sat, Sep 22, 2018 at 8:52 AM Anders Hovmöller
wrote:
> >>> I think that entire paragraph made it sound even worse than what I
> wrote originally. It reads to an outsider as “if you don’t know what’s
> wrong I’m not going to tell you”.
> >
> > More like, if you're not sufficiently familiar with
On 09/22/2018 05:52 AM, Anders Hovmöller wrote:
And now you made it sound even worse [...]
Their use of the word "you" is "everybody who wants to write a PEP", not
you "Anders Hovmöller" specifically. (Isn't English a wonderful
language? *sigh* )
--
~Ethan~
__
>> And now you made it sound even worse by insinuating that I don’t know the
>> language and maybe I’m not a part of the community.
>
> Anders, I'm sorry you feel that everyone is piling onto you.
Well a bit, but mostly I was just pointing out that the text I replied to
wasn’t thought out an
Anders Hovmöller writes:
> > If one doesn't know who the senior developers are yet, she should
> > think twice about whether she's ready to PEP anything. That's
> > not a litmus test; some PEPs have eventually succeeded though the
> > proponent was new to the project development process.[2]
> To my mind, there is one very big reason we should be cautious about
> adopting JS language-design policies, namely, that they have led to a
> very, very poorly designed language. No doubt a good deal of that is
> baggage from early stages in which JS had a poor to nonexistent language
> des
>>> If one doesn't know who the senior developers are yet, she should
>>> think twice about whether she's ready to PEP anything. That's
>>> not a litmus test; some PEPs have eventually succeeded though the
>>> proponent was new to the project development process.[2] But it's
>>> a lot less pain
On Sat, Sep 22, 2018 at 2:00 PM Stephen J. Turnbull
wrote:
> If one doesn't know who the senior developers are yet, she should
> think twice about whether she's ready to PEP anything.
On Sat, Sep 22, 2018 at 4:03 PM Anders Hovmöller wrote:
> Is there a committee? Then why not just name it?
> How
On Sat, Sep 22, 2018 at 4:53 AM Lee Braiden wrote:
> Problem: [Python] prevents actual default argument values being set in a
> function signature
> Feedback would be much appreciated.
You'd be more convincing if you stated the problem more precisely.
Python supports default values for function
Hi,
(I'd like to fork from a previous thread, "Pre-conditions and
post-conditions", since it got long and we started discussing a couple of
different things. Let's put the general discussion related to
design-by-contract in this thread and I'll spawn another thread for the
discussion about the con
Hi,
(I'd like to fork from a previous thread, "Pre-conditions and
post-conditions", since it got long and we started discussing a couple of
different things. Let's discuss in this thread the implementation of a
library for design-by-contract and how to push it forward to hopefully add
it to the st
27 matches
Mail list logo
