[Python-Dev] Re: Call for papers for PyCon 2020

2020-09-13 Thread Claudio Jolowicz 
Dear Amna, thank you for your interest in my talk, and sorry for the late
reply. Unfortunately, I won't be able to make it this year. Please feel
free to reach out again in the future. Wishing you all the best, and thank
you for organizing this conference :) Claudio

On Thu, 6 Aug 2020 at 18:22, Amna Ahsan  wrote:

> Hi,
>
> I am writing to you on behalf of PyCon Estonia  to
> invite you to take part in the call for papers for our 2020 edition and
> join us as a speaker at PyCon: https://pyconestonia.typeform.com/to/e0jriV
>
>
> This is the third PyCon Estonia event after successful delivery in 2018
> and 2019. PyCon Estonia is organised by our NGO Python Estonia
>  which is dedicated to education and awareness
> about Python in the region.
>
> In previous years , keynote
> speakers at PyCon Estonia have included Travis Oliphant (Creator of
> NumPy) and Kristo Vaher (Govt. CTO of Estonia). We've had around 300
> participants join us for a live conference in Tallinn, Estonia with 7-9
> excellent speakers from all walks of life talking about Python. This year
> we already have Miguel Grinberg  as one
> of our speakers.
>
> Due to coronavirus, this PyCon will be an entirely virtual conference,
> possibly with a bigger and more international audience. The theme for
> PyCon Estonia 2020 is "The power of Python" and we want to talk about the
> real life applications of Python and how digital products built on Python
> are impacting the tech sector or the world in general.
>
> We would really like to have you offer a possible topic for a talk at
> PyCon. We intend to have a total of 8 talks of 30-minutes followed by a
> 10-minute Q&A. If this would be something you are interested in, please
> submit a proposal here: https://pyconestonia.typeform.com/to/e0jriV
> before the *15th August, 2020*.
>
> I am happy to add that we are a diverse group organising PyCon Estonia
> 2020, and we are trying to make the conference as diverse as possible.
>
> If you have any questions, please don't hesitate to write to me.
>
> Best Regards,
>
> *Amna Ahsan*
> Chief Marketing Officer
>
> *Python Estonia*
> +372 5784 0436
> ___
> Python-Dev mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> https://mail.python.org/mailman3/lists/python-dev.python.org/
> Message archived at
> https://mail.python.org/archives/list/[email protected]/message/VR3Y7HSHVPL3T4NGN7YQ7HJ5SOBIO4XD/
> Code of Conduct: http://python.org/psf/codeofconduct/
>
___
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/XFQE7VRKMA3TLYBKKY3RD7HEBO263TYS/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] docs: I'd like new features to references their PEPs

2020-09-13 Thread Cameron Simpson 
So, today I noticed __length_hint__, and then operator.length_hint.  
Neither mentions its design purpose, only its specification. And while 
that is minimally enough, knowing the purpoe (size estimation for use by 
presized allocation operations) lets an implementor write something more 
appropriate.

While it'd be nice to have a short sentence with the provoking rationale 
for the feature in the docs, it would also be nice to reference the PEP.

As a concrete example, for __length_hint__ and operator.length_hint, I 
wish that in addition to saying "New in version 3.4", it also said 
"specified by PEP424 [link]", since I had to go find that with a search 
engine to understand the rationale.

Would PRs with such patches be welcome?

Cheers,
Cameron Simpson 
___
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/HXNFMIEZH73MXYEBP4TDIK3KFPYJ4QKR/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: docs: I'd like new features to references their PEPs

2020-09-13 Thread Guido van Rossum 
On Sun, Sep 13, 2020 at 8:12 PM Cameron Simpson  wrote:

> So, today I noticed __length_hint__, and then operator.length_hint.
> Neither mentions its design purpose, only its specification. And while
> that is minimally enough, knowing the purpoe (size estimation for use by
> presized allocation operations) lets an implementor write something more
> appropriate.
>
> While it'd be nice to have a short sentence with the provoking rationale
> for the feature in the docs, it would also be nice to reference the PEP.
>
> As a concrete example, for __length_hint__ and operator.length_hint, I
> wish that in addition to saying "New in version 3.4", it also said
> "specified by PEP424 [link]", since I had to go find that with a search
> engine to understand the rationale.
>
> Would PRs with such patches be welcome?
>

Yeah, I think that's a reasonable idea, and I don't think it needs a news
item or bpo bug either. If you know there's a PEP you should be able to
find it through the what's new doc for the version where the feature was
added (assuming there's a "versionadded" note), but that's pretty indirect,
and people might not even think there could be a PEP.

A downside of linking to the PEP is that sometimes the PEP has an outdated
version of an API. For example asyncio has evolved quite a bit since PEP
3156 (some stuff in the PEP turned out not so hot), and I'm sure that's not
the only case. But all in all I like the idea of linking to the PEP from
the "versionadded" or "versionchanged" note.

-- 
--Guido van Rossum (python.org/~guido)
*Pronouns: he/him **(why is my pronoun here?)*

___
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/ZGA7ZQDTYYTUTDGILCYDD45YXTSEFDWK/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: docs: I'd like new features to references their PEPs

2020-09-13 Thread Cameron Simpson 
On 13Sep2020 20:51, Guido van Rossum  wrote:
>On Sun, Sep 13, 2020 at 8:12 PM Cameron Simpson  wrote:
>> As a concrete example, for __length_hint__ and operator.length_hint, 
>> I
>> wish that in addition to saying "New in version 3.4", it also said
>> "specified by PEP424 [link]", since I had to go find that with a search
>> engine to understand the rationale.
[...]
>A downside of linking to the PEP is that sometimes the PEP has an 
>outdated
>version of an API. For example asyncio has evolved quite a bit since PEP
>3156 (some stuff in the PEP turned out not so hot), and I'm sure that's not
>the only case. But all in all I like the idea of linking to the PEP from
>the "versionadded" or "versionchanged" note.

Happy to use the term "originally specified by PEP424 [link]" :-)

I'll make some PRs. How to submit? Here, or a BPO or something?

Cheers,
Cameron Simpson 
___
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/HO25HHHUBKETJYXWQ2Y7JTANALC6SRBS/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: docs: I'd like new features to references their PEPs

2020-09-13 Thread Ned Deily 
On Sep 14, 2020, at 01:07, Cameron Simpson  wrote:
> On 13Sep2020 20:51, Guido van Rossum  wrote:
>> On Sun, Sep 13, 2020 at 8:12 PM Cameron Simpson  wrote:
>>> As a concrete example, for __length_hint__ and operator.length_hint, 
>>> I
>>> wish that in addition to saying "New in version 3.4", it also said
>>> "specified by PEP424 [link]", since I had to go find that with a search
>>> engine to understand the rationale.
> [...]
>> A downside of linking to the PEP is that sometimes the PEP has an 
>> outdated
>> version of an API. For example asyncio has evolved quite a bit since PEP
>> 3156 (some stuff in the PEP turned out not so hot), and I'm sure that's not
>> the only case. But all in all I like the idea of linking to the PEP from
>> the "versionadded" or "versionchanged" note.
> Happy to use the term "originally specified by PEP424 [link]" :-)
> 
> I'll make some PRs. How to submit? Here, or a BPO or something?

My suggestion would be to open one BPO issue for "adding PEP references to 
documentation" and then creating PRs as needed against it.  As you probably 
know, the devguide has the details including for the inline markup role :pep:.

https://devguide.python.org/documenting/#rest-inline-markup

--
  Ned Deily
  [email protected] -- []
___
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/OEWCJIXELLPJXWIXJU6FNBG7UMOLOP6W/
Code of Conduct: http://python.org/psf/codeofconduct/