[python-committers] Re: Zackery Spytz got the bug triage permission

2019-06-06 Thread Christian Heimes
On 07/06/2019 00.12, Victor Stinner wrote:
> Hi,
> 
> I decided to give more responsibilities to Zackery Spytz as a reward
> for his hard commitment over the last year and a half into Python: I
> gave him the bug triage permission.

+1

I worked with him on a couple of bugs, e.g. the memfd_create. He does a
good job.

Christian
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/WUZNQLX2GAETCZT62SRLL7NYDLYH7Y7F/
Code of Conduct: https://www.python.org/psf/codeofconduct/


[python-committers] Re: Zackery Spytz got the bug triage permission

2019-06-06 Thread Andrew Svetlov
+1

On Fri, Jun 7, 2019 at 2:03 AM Carol Willing  wrote:
>
> Congrats Zackery! Thanks for the contributions too.
>
> On Thu, Jun 6, 2019 at 3:12 PM Victor Stinner  wrote:
>>
>> Hi,
>>
>> I decided to give more responsibilities to Zackery Spytz as a reward
>> for his hard commitment over the last year and a half into Python: I
>> gave him the bug triage permission.
>>
>> He managed to get not less than 111 changes merged into the master
>> branch since February 2018!
>> https://github.com/python/cpython/commits?author=ZackerySpytz
>> https://github.com/python/cpython/pulls/ZackerySpytz
>>
>> He usually document properly his change and add new tests. He is not
>> afraid of touching the C code base and working in the dark Python
>> internals. He also likes to get reviews, and updates his change to
>> take comments in account.
>>
>> Example of changes.
>>
>> bpo-37007: Implement socket.if_nametoindex(), if_indextoname() and
>> if_nameindex() on Windows
>> https://github.com/python/cpython/pull/13522
>>
>> bpo-26836: Add os.memfd_create()
>> https://github.com/python/cpython/pull/13567
>>
>> bpo-33407: Implement Py_DEPRECATED() on MSVC
>> https://github.com/python/cpython/pull/8980
>>
>> bpo-32941: Add madvise() for mmap objects
>> https://github.com/python/cpython/pull/6172
>>
>> He also fixed numerous bugs all around the code base, making Python
>> more stable and safer to use!
>>
>> I sent Zackery instructions how to triage bug and links into the devguide.
>> I required him to ask me before closing a bug. I also offered to
>> mentor him for 1 month, to help him to handle his new
>> responsibilities.
>>
>> Congrats Zackery ;-) (I added him in copy of this email)
>>
>> Victor
>> --
>> Night gathers, and now my watch begins. It shall not end until my death.
>> ___
>> python-committers mailing list -- python-committers@python.org
>> To unsubscribe send an email to python-committers-le...@python.org
>> https://mail.python.org/mailman3/lists/python-committers.python.org/
>> Message archived at 
>> https://mail.python.org/archives/list/python-committers@python.org/message/IMYXXTA2VN44ASGA33D7LVUZEWKEAUCQ/
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
> --
> Carol Willing
>
> Willing Consulting
>
> Signature strengths
> Empathy - Relator - Ideation - Strategic - Learner
> ___
> python-committers mailing list -- python-committers@python.org
> To unsubscribe send an email to python-committers-le...@python.org
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at 
> https://mail.python.org/archives/list/python-committers@python.org/message/SZPZHRUM7Z4TCP3IMGDZ5TKBGZIHZCDK/
> Code of Conduct: https://www.python.org/psf/codeofconduct/



-- 
Thanks,
Andrew Svetlov
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/Z5LTXJRCYO6FOPLD2BL4RHYCQTA4U55L/
Code of Conduct: https://www.python.org/psf/codeofconduct/


[python-committers] Re: Zackery Spytz got the bug triage permission

2019-06-06 Thread Carol Willing
Congrats Zackery! Thanks for the contributions too.

On Thu, Jun 6, 2019 at 3:12 PM Victor Stinner  wrote:

> Hi,
>
> I decided to give more responsibilities to Zackery Spytz as a reward
> for his hard commitment over the last year and a half into Python: I
> gave him the bug triage permission.
>
> He managed to get not less than 111 changes merged into the master
> branch since February 2018!
> https://github.com/python/cpython/commits?author=ZackerySpytz
> https://github.com/python/cpython/pulls/ZackerySpytz
>
> He usually document properly his change and add new tests. He is not
> afraid of touching the C code base and working in the dark Python
> internals. He also likes to get reviews, and updates his change to
> take comments in account.
>
> Example of changes.
>
> bpo-37007: Implement socket.if_nametoindex(), if_indextoname() and
> if_nameindex() on Windows
> https://github.com/python/cpython/pull/13522
>
> bpo-26836: Add os.memfd_create()
> https://github.com/python/cpython/pull/13567
>
> bpo-33407: Implement Py_DEPRECATED() on MSVC
> https://github.com/python/cpython/pull/8980
>
> bpo-32941: Add madvise() for mmap objects
> https://github.com/python/cpython/pull/6172
>
> He also fixed numerous bugs all around the code base, making Python
> more stable and safer to use!
>
> I sent Zackery instructions how to triage bug and links into the devguide.
> I required him to ask me before closing a bug. I also offered to
> mentor him for 1 month, to help him to handle his new
> responsibilities.
>
> Congrats Zackery ;-) (I added him in copy of this email)
>
> Victor
> --
> Night gathers, and now my watch begins. It shall not end until my death.
> ___
> python-committers mailing list -- python-committers@python.org
> To unsubscribe send an email to python-committers-le...@python.org
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-committers@python.org/message/IMYXXTA2VN44ASGA33D7LVUZEWKEAUCQ/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
-- 
*Carol Willing*

Willing Consulting 

*Signature strengths*
*Empathy - Relator - Ideation - Strategic - Learner*
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/SZPZHRUM7Z4TCP3IMGDZ5TKBGZIHZCDK/
Code of Conduct: https://www.python.org/psf/codeofconduct/


[python-committers] Re: python-committers is now running on Mailman 3

2019-06-06 Thread Ɓukasz Langa
Thanks! This message is posted directly from HyperKitty.
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/QKI6ANMYZ2DBTLDQRKV2TN3UPJS7BXMS/
Code of Conduct: https://www.python.org/psf/codeofconduct/


[python-committers] Zackery Spytz got the bug triage permission

2019-06-06 Thread Victor Stinner
Hi,

I decided to give more responsibilities to Zackery Spytz as a reward
for his hard commitment over the last year and a half into Python: I
gave him the bug triage permission.

He managed to get not less than 111 changes merged into the master
branch since February 2018!
https://github.com/python/cpython/commits?author=ZackerySpytz
https://github.com/python/cpython/pulls/ZackerySpytz

He usually document properly his change and add new tests. He is not
afraid of touching the C code base and working in the dark Python
internals. He also likes to get reviews, and updates his change to
take comments in account.

Example of changes.

bpo-37007: Implement socket.if_nametoindex(), if_indextoname() and
if_nameindex() on Windows
https://github.com/python/cpython/pull/13522

bpo-26836: Add os.memfd_create()
https://github.com/python/cpython/pull/13567

bpo-33407: Implement Py_DEPRECATED() on MSVC
https://github.com/python/cpython/pull/8980

bpo-32941: Add madvise() for mmap objects
https://github.com/python/cpython/pull/6172

He also fixed numerous bugs all around the code base, making Python
more stable and safer to use!

I sent Zackery instructions how to triage bug and links into the devguide.
I required him to ask me before closing a bug. I also offered to
mentor him for 1 month, to help him to handle his new
responsibilities.

Congrats Zackery ;-) (I added him in copy of this email)

Victor
-- 
Night gathers, and now my watch begins. It shall not end until my death.
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/IMYXXTA2VN44ASGA33D7LVUZEWKEAUCQ/
Code of Conduct: https://www.python.org/psf/codeofconduct/


[python-committers] Vote to promote Paul Ganssle as a core developer

2019-06-06 Thread Pablo Galindo Salgado

*
The vote is happening here:
https://discuss.python.org/t/vote-to-promote-paul-ganssle-as-a-core-developer/1826

*
Victor Stinner and I want to propose Paul Ganssle as a core developer, who
would center his efforts on co-maintaining datetime together with Alexander
Beloposky.

Some of you may already know Paul Ganssle as the main maintainer of
dateutil, as maintainer of setuptools or for his contributions to CPython.
On the technical side, Paul has proven many times to have a great domain
knowledge around the datetime module and related functionality but he also
has remarkable knowledge about Python and CPython internals. As a reviewer,
Paul has made several reviews of datetime-related pull requests but also
other general pull requests involving Python
and C code as well as documentation. In the reviews he always shows a great
care towards the contributor (as can be seen as well in the reviews in the
packages that Paul maintains) but also he has spend a lot of time reviewing
the wording as a native English speaker, always in a detailed and
pedagogical way. Paul always listens to other ideas and viewpoints when
discussing and he reacts very positively to criticism in his PRs and work.

Paul would like to focus on co-maintain datetime together with Alexander
Beloposky (who has expressed that he is ok with that).

We consulted with Paul prior to the nomination, and he said he is
interested in becoming a core developer so that he can expand his ability
to improve the datetime module and CPython in general; he also participates
in many sprint events, and it would improve his ability to bring new
contributors on to the project. In short, we think Paul is an exceptional
developer, a kind and compassionate person, and CPython would benefit from
having him on the core team.

I have oppened a vote on discuss.python.org (
https://discuss.python.org/t/vote-to-promote-paul-ganssle-as-a-core-developer/1826)
for 1 week. As a reminder from PEP 13 regarding voting rules:

>... It is granted by receiving at least two-thirds positive votes in a
core team vote that is open for one week and with no veto by the steering
council."
https://www.python.org/dev/peps/pep-0013/#membership

Here is a summary of Paul's work and achievements:

## Background Information about Paul Ganssle

1. Maintainer of dateutil since 2014. First and most prominent third-party
implementation of PEP 495 (Local Time Disambiguation).
2. Maintainer of setuptools since 2018.
3. Frequently run sprints on dateutil and setuptools. Would like to be able
to offer mentorship on CPython at conference sprints.
4. Organized and ran the PyPA mini-summit at PyCon US 2018 and 2019, active
in the PyPA generally.
5. Wrote datetime bindings for PyO3 (CPython bindings for Rust), and has
continued to contribute regularly to that project with PRs, reviews and
issues. Interested in contributing to the C API from the perspective of
someone writing cross-language bindings.
6. Frequently helps maintain datetime-related code on other projects:
- `pandas`: [Issue 23959](
https://github.com/pandas-dev/pandas/issues/23959), [issue 18523](
https://github.com/pandas-dev/pandas/issues/18523), [PR 19281](
https://github.com/pandas-dev/pandas/pull/19281), [PR 22560](
https://github.com/pandas-dev/pandas/pull/22560)
- `matplotlib`: [PR 12678](
https://github.com/matplotlib/matplotlib/pull/12678), [issue 9018](
https://github.com/matplotlib/matplotlib/issues/9018), [PR 11610](
https://github.com/matplotlib/matplotlib/pull/11610), [PR 11360](
https://github.com/matplotlib/matplotlib/pull/11360)
- `jupyter`: [jupyter-widgets/ipywidgets#168](
https://github.com/jupyter-widgets/ipywidgets/issues/168#issuecomment-147581117
)
7. Spoke at the language summit about adding more time zones to the
standard library. [Slides](
https://pganssle-talks.github.io/pycon-us-2019-language-summit-tz/#/),
[Repo](https://github.com/pganssle-talks/pycon-us-2019-language-summit-tz)

### Major accomplishments in CPython

1. Implemented `datetime.fromisoformat`, the inverse of
`datetime.isoformat`. This is still the fastest constructor for `datetime`
accessible from Python. ([PR #4699](
https://github.com/python/cpython/pull/4699), [PR #8959](
https://github.com/python/cpython/pull/8959))
2. Exposed `datetime.timezone` and `datetime.timezone.utc` in the CPython
API. ([PR #5032](https://github.com/python/cpython/pull/5032))
3. Implemented and made the case for changing the return type of `datetime`
+ `timedelta` arithmetic to respect the subclass of the `datetime` object.
Similarly has been working to make `datetime` safer to subclass in general.
([PR #10902](https://github.com/python/cpython/pull/10902), [Python-dev
thread 1](