tes.
During the next phase I will work with the WG to sort out all the
major issues that we might encounter, and then I will once again reach
out to you to gather feedback from the wider audience that follows
these mailing lists.
Best Regards,
Ezio Melotti
__
://www.python.org/dev/peps/pep-0588/
The full text of the PEP is include below. We are planning to update
the PEP to include the feedback we receive and to update the status of
features as we implement them (we also have a Google Summer of Code
students working on it).
Best Regards,
Ezio Melotti
ansparent, without
considering some of the concerns.
(This might also be a symptom of a wider problem caused by the
fragmentation of the discussions between the old MLs, discuss, zulip,
IRC, GitHub PRs and issues, and IRL meetings, but this is a separate
topic.)
Best Regards,
Ezio Melotti
On Sun, Apr 28, 2019 at 11:58 PM Guido van Rossum wrote:
>
> On Sun, Apr 28, 2019 at 2:05 PM Ezio Melotti wrote:
>>
>> On Sat, Apr 27, 2019 at 10:44 PM Guido van Rossum wrote:
>> >
>> > On Sat, Apr 27, 2019 at 11:10 AM Victor Stinner
>> > wrote
On Sat, Apr 27, 2019 at 10:44 PM Guido van Rossum wrote:
>
> On Sat, Apr 27, 2019 at 11:10 AM Victor Stinner wrote:
>>
>> Would it be possible to discuss these PEPs on python-dev? Or is it a
>> deliberate choice to not let non core dev to be involved in the discussion?
>
>
> It was not a deliber
several non-trivial patches there.
>
The meta tracker at upfronthosting is gone for good, but nothing is
lost, we have backups and can retrieve the patches if we need them.
Best Regards,
Ezio Melotti
> --Berker
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/
tLab versus some other
> issue tracker (open or closed source, self-hosted or service-hosted I
> personally don't care; heck write it from scratch like Warehouse if that's
> what it takes), but unless we get some people to step forward to he
+1
On Thu, Jan 25, 2018 at 12:23 AM, Yury Selivanov
wrote:
> Hi,
>
> I want to propose granting commit privileges to Nathaniel J. Smith.
> He's interested in the idea of becoming a core developer, and given
> the quality of his contributionsI think he won't need any extensive
> mentoring (althoug
Done as well!
On Mon, Dec 18, 2017 at 3:47 PM, Victor Stinner
wrote:
> Oh, Julien told me that he doesn't have the bug triage permission
> neither. Would you mind to allow him to close bugs as well? :-)
>
> Victor
>
> 2017-12-18 14:57 GMT+01:00 Ezio Melotti :
>> On
.python.org/user23063
>
> His nick name is "mdk". Can someone please fix his bpo account?
>
Done, and welcome to the team Julien!
Best Regards,
Ezio Melotti
> Devguide: https://devguide.python.org/coredev/#issue-tracker
>
> Victor
On Fri, Dec 8, 2017 at 5:32 PM, Victor Stinner wrote:
> 2017-12-08 17:19 GMT+01:00 Ezio Melotti :
>>> Aha. Maybe we need some tooling, like statistics on contributions to the
>>> bug tracker, just to detect earlier active "bug triagers"?
>>>
>>
>&g
cess, ISTM
they are also making it more bureaucratic.
>
> R. David Murray :
>>> Maybe we can give some guide lines on how to behave on the bug
>>> tracker?
>>
>> Enhance the bug triage section of the devguide, by all means :)
>
> To not forget, I created
were still plenty of low hanging fruits on the bug tracker
or other issues to work on. Then Python 3 came, and there was more
work to be done.
Nowadays the situation is much better, Python is more stable and
mature, and what's left is more difficult, obscure, or controversial.
There are still new modules and features being added and ISTM that
most of the new core devs are working on those (e.g.
asyncio/typing/etc), but otherwise finding new easy issues is becoming
increasingly more difficult.
Best Regards,
Ezio Melotti
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/
in general;
2) reach to the mentor only when necessary (i.e. no one else replied,
something import/urgent/"personal").
For GSoC the situation is different:
1) GSoC students have to work on a specific project with specific
goals, requirements, and deadlines;
2) GSoC students are usually less expe
If the contributor knows what they are doing and they
are helpful, we can "award" them with the triager bit, but this award
shouldn't be given for unrelated accomplishments.
Becoming a triager is a step to becoming a committer: we bestow them
with some responsibility and trust, and
ned procedure and sometimes people keep contributing for
weeks before someone realizes they could become triagers.
To avoid this, we can either:
1) let contributors know that they could ask for more power if they
think they can handle it;
2) be more proactive and check regularly if there are contrib
ople took over with not many repercussions. For more
specific areas (e.g. html.parser or Unicode) I still try to participate to
the discussions. For the bug tracker I have to commit long-term because
other devs lack the time and/or knowledge required to maintain it.
Best Regards,
Ezio Melotti
>
lity falls on the
author/comitter (i.e. the core-dev). If core devs merge their own patches,
the responsible will always be the committer.
If you merge other core devs' patches, you are likely to get blamed when
something breaks even if the c
On Fri, Aug 11, 2017 at 5:22 PM, Barry Warsaw wrote:
> On Jul 12, 2017, at 12:00, Ezio Melotti wrote:
>
> > Both the SFO and SJC airports seem to be close to Menlo Park. Is there
> any preference on the airport? Does the hotel provide any shuttle service?
>
> Personally, I
firm your
> hotel room until I have your flight information.
>
> *Full list of confirmed attendance:*
> zware
> ned-deily
> ncoghlan
> warsaw
> benjaminp
> tiran
> ericvsmith
> 1st1
> larryhastings
> ericsnowcurrently
> Mariatta
> ezio-melotti
> applio
&
Hi,
I signed up but haven't heard any news yet.
September is approaching, so it would be great to know if you are still
deciding/negotiating or if you already know the names :)
Best Regards,
Ezio Melotti
On Tue, Jun 13, 2017 at 1:04 AM, Lukasz Langa wrote:
> Hello fellow committer
er that there is something that needs to
> automated about numbers.
>
> What I would like is that the BPO issue # in the PR title be a link so it is
> easy to jump from PR to BPO.
>
There are some discussion about it, I think on the core-workflow issue tracker.
I'm
easily debug issue613) and eventually we will put the image
on DockerHub.
> Fifth, anything I missed? :)
>
I find the documentation in the devguide still lacking.
I've been trying to improve it, but first I have to figure out all the
details of the new workflow.
Best Regards,
ixed it in the meanwhile.
Best Regards,
Ezio Melotti
> ... which displays short error message:
> ---
> Usage: /lookup/GITHEXHASH or gitGITHEXHASH (10, 11, or 40 hex characters)
> /lookup/HGHEXNODE or hgHGHEXNODE (12 or 40 hex characters)
> /lookup/rSVNREVISION
> ---
>
&g
ention the author instead of
> the commiter? Or maybe mention both?
>
If GitHub passes the information along (and it probably does), then it
should be possible to have both.
Please create an issue on the meta-tracker to keep track of this.
Best R
rejected due to the bad cert then it would have been dropped.
>
Today I also spotted and fixed another issue, and verified that now
the messages are showing up on bpo (see e.g.
http://bugs.python.org/issue29557#msg287801). Let me know if there
are other issues.
Best Regards,
Ezio Melotti
&g
the PRs would then only be for code review
> aspects.
>
Yes, discussions on the PRs replace the discussions we had on Rietveld
-- they should only be about the code review.
Best Regards,
Ezio Melotti
> Thanks,
> --
> Marc-Andre Lemburg
> eGenix.com
I've been keeping an eye on the tracker logs and saw no errors. If
you are still having problems after the SSL fix let me know.
On Mon, Feb 13, 2017 at 8:16 PM, Brett Cannon wrote:
> There was an issue up until sometime on Sunday where the SSL cert for
> bugs.python.org was being rejected (it wa
;
5) the more time I spend away, the more difficult it becomes to follow
all the new features that get introduced.
As for what would get me involved again, for my case there's not much
else you can do -- I just need to find more free time, catch up with
development (mails, tools, features,
On Sat, Dec 24, 2016 at 12:37 AM, Victor Stinner
wrote:
> 2016-12-23 19:07 GMT+01:00 Brett Cannon :
>> Maciej has been helping Ezio, David, and me out with updates to
>> bugs.python.org for the GitHub migration and he's reached a point where we
>> are all comfortable with him making updates to the
however serve as a
remainder to people that disregard (intentionally or not) these
principles, and help shaping the image of our community for external
people -- including potential new members of our community.
Best Regards,
Ezio Melotti
[0]: "A code of conduct is a set of rules o
On Tue, Feb 2, 2016 at 4:54 PM, R. David Murray wrote:
> On Tue, 02 Feb 2016 15:33:58 +0200, Ezio Melotti
> wrote:
>> On Sat, Jan 30, 2016 at 5:36 AM, Guido van Rossum wrote:
>> > Following the lead of 2.7.10 and 2.7.11 we could continue with 3.10, 3.11,
>> > etc
On Sat, Jan 30, 2016 at 4:08 AM, Martin Panter wrote:
>> What and when to deprecate
>> ==
>>
>> * The number of releases before an API is removed is decided
>> on a case-by-case basis depending on widely used the API is
>
> depending on [how] widely used
>
>> * In general
On Fri, Jan 29, 2016 at 11:59 PM, Serhiy Storchaka wrote:
> On 29.01.16 21:56, Ezio Melotti wrote:
>>
>> On Fri, Jan 29, 2016 at 8:00 PM, Serhiy Storchaka
>> wrote:
>>>
>>> What about adding deprecations in bugfix releases? If current behavior is
>>
On Sat, Jan 30, 2016 at 5:36 AM, Guido van Rossum wrote:
> Following the lead of 2.7.10 and 2.7.11 we could continue with 3.10, 3.11,
> etc.
>
I think we should continue with 3.10, 3.11, etc.
Changing the major version should be done for incompatible changes,
and just doing it after 3.9 will pro
On Sat, Jan 30, 2016 at 1:39 AM, Barry Warsaw wrote:
> On Jan 29, 2016, at 06:11 PM, Brett Cannon wrote:
>
>>+1 from me as well, especially once Serhiy's comments are addressed.
>
> Me too, but only if you add a PendingDeprecationWarning to
> PendingDeprecationWarning .
>
The original plan actual
On Fri, Jan 29, 2016 at 8:00 PM, Serhiy Storchaka wrote:
> On 29.01.16 19:11, Ezio Melotti wrote:
>>
>> Deprecation Warnings
>>
>>
>> Python offers two kinds of deprecation warnings:
>>
>> * ``PendingDeprecationWarning``
>
discussions on python-dev and related issues.
Best Regards,
Ezio Melotti
-
PEP: XXX
Title: Deprecation Policy
Version: $Revision$
Last-Modified: $Date$
Author: Ezio Melotti
Status: Draft
Type: Process
Content-Type: text/x-rst
Created: 29-Jan-2016
Post-History:
Abstract
The goal of
te of
> comment" info available? If so, it could fairly readily assume that
> hashes prior to the cutover date are hg ones, and later ones are for
> git.
By looking at the code I don't see it readily available, but it might
be possible to retrieve it somehow.
However I think it'
figure out if the
csid is from hg or git and redirect where more appropriate.
Best Regards,
Ezio Melotti
On Tue, Jan 5, 2016 at 3:37 AM, Alex Gaynor wrote:
> Probably the easiest thing is to point the linkifier at our own webservice
> that just does:
>
> if hash not in cach
uot;never send to spam".
The issue is also being discussed at
http://psf.upfronthosting.co.za/roundup/meta/issue562
Best Regards,
Ezio Melotti
> Yury
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Hi,
On Fri, Jan 9, 2015 at 11:47 PM, M.-A. Lemburg wrote:
> On 09.01.2015 23:26, Ezio Melotti wrote:
>> Hi,
>>
>> On Fri, Jan 9, 2015 at 1:09 PM, M.-A. Lemburg wrote:
>>>
>>> BTW: How about having an "incubator" phase for new core devs ?
>&
ree month period is not necessary, if
they cause trouble we will just revoke the right (but that shouldn't
happen).
Best Regards,
Ezio Melotti
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
ividually.
He followed my suggestion and sent the list, but iirc no one replied, so he
probably deemed the approach ineffective and went back to pinging the
issues.
I also suggested him to work on the bug tracker code or on similar projects
-- not sure if he gave that a try yet.
Best Regards,
Ezio M
r a few weeks before he pinged the thread
only to be ignored again, so this method seems somewhat effective.
(And FTR I don't think I'm wasting my time -- if anything I'm
sharpening my already nearly-limitless patience ;).
Best Regards,
Ezio Melotti
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
On Wed, Nov 20, 2013 at 10:34 PM, Antoine Pitrou wrote:
> On mer., 2013-11-20 at 21:57 +0200, Ezio Melotti wrote:
>> Now I'm working on #13633 (Automatically convert character references
>> in HTMLParser [1]), and I'm planning to add a convert_charrefs boolean
>>
to add a generator-based API [3], but that's a major change and I need
more time to think about it.
Best Regards,
Ezio Melotti
[0]: http://www.w3.org/TR/html5/syntax.html
[1]: http://bugs.python.org/issue13633 - Automatically convert
character references in HTMLParser
[2]: http://bugs.python.
tion to the team.
I can also help supervising him if necessary.
Best Regards,
Ezio Melotti
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
h to solve it.
>>
>> Technically it's an infrastructure issue (cc'd), but fixing the code of
>> roundup is hardly their domain.
>>
>> Ezio Melotti (cc'd) did a lot of work on the Python installation of roundup,
>> so he may have a better ide
iscussed informally during the conference if
someone is interested.
Best Regards,
Ezio Melotti
> If I get a lot of topics
> I'll inquire about getting a room set aside for a couple of hours.
>
> Cheers,
>
>
> /arry
___
python-c
Hi,
are there any plans about doing a language summit at EuroPython this year?
Best Regards,
Ezio Melotti
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers
On Tue, May 28, 2013 at 9:47 PM, Terry Reedy wrote:
> On 5/28/2013 10:19 AM, Dirkjan Ochtman wrote:
>>
>> It's possible something broke with the @-filename.
>
> I am planning to change '@' to '_' anyway.
>
What's wrong with just
also be doable.
>> And do
>> we really need a merged NEWS file at that granularity?
>
> Not really, IMO.
>
I'm +0 on having a separate file for 3.3, 3.4, etc., as long as I
don't have to copy/paste the news entry in the right file every time.
Anything more than that i
ing of all issue fields). Which is why triage people appear in the
> assigned-to even though they aren't committers (yet :).
>
Correct.
> The committer flag only controls the icon, as far as I remember.
>
FTR the "nosy" autocomplete u
u ever receive any reply
from the real lawyer?
Best Regards,
Ezio Melotti
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers
f course it
could also be a misunderstanding of the license terms from his part,
but in this case he would probably want a clarification.
Best Regards,
Ezio Melotti
>
> cheers,
> Georg
>
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers
Hi,
On Tue, Jan 1, 2013 at 11:55 PM, Brian Curtin wrote:
> On Tue, Jan 1, 2013 at 3:49 PM, Ezio Melotti wrote:
>> Hi,
>>
>> On Tue, Jan 1, 2013 at 10:57 PM, Georg Brandl wrote:
>>> On 01/01/2013 05:54 PM, Ezio Melotti wrote:
>>>
>>>> I sa
Hi,
On Tue, Jan 1, 2013 at 10:57 PM, Georg Brandl wrote:
> On 01/01/2013 05:54 PM, Ezio Melotti wrote:
>
>> I say Ezio lets him know that this is the plan since he talked to him
>> recently and is in the no-ban-yet camp.
>>
>>
>> Yesterday I t
what the issue is today.
>
AFAIU he's willing to sign it again -- nonetheless the issues
mentioned in my previous mail remain.
Best Regards,
Ezio Melotti
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers
Hi,
On Tue, Jan 1, 2013 at 7:06 PM, Jesse Noller wrote:
> On Jan 1, 2013, at 11:54 AM, Ezio Melotti wrote:
>
> Hi,
>
> [...]
>
> We also discussed about the contributor agreement and IIUC:
> 1) he signed it already 1.5 years ago but apparently it got lost (that
> wo
e the PSF doesn't
follow the terms and requirements of the linked Apache 2 license (and while
he doesn't seem against signing in, that would be quite pointless if it was
indeed invalid);
3) he said that an electronic signature like the one at the bottom of
http://code.google.com/legal/indi
sues. If he really thinks important
> information was not considered, he can post them to the closed issue.
> - he must not resubmit a duplicate of one of his closed issues.
>
>
I think I mentioned this last time we talked, and I'll make sure to make it
clearer next time.
Best
On Wed, Dec 26, 2012 at 7:37 PM, R. David Murray wrote:
> On Wed, 26 Dec 2012 18:20:06 +0200, Ezio Melotti
> wrote:
> > On Wed, Dec 26, 2012 at 5:07 PM, Łukasz Langa wrote:
> > > I don't want to spell out names but I've had more than one discussion
> at
>
K, so I wonder if "our" opinion
towards him is already negatively biased and leads us to be less tolerant
with him
At the end he thanked me for bringing this up with him, and apparently he
is willing to improve.
Best Regards,
Ezio Melotti
___
On Wed, Dec 26, 2012 at 5:07 PM, Łukasz Langa wrote:
> Dnia 26 gru 2012 o godz. 15:09 Ezio Melotti
> napisał(a):
>
> > The community should ignore the tone of the messages or even the
> messages themselves and most importantly avoid replies that convey the same
> negat
e previous attempts to address the
problem were unsuccessful. I'm willing to make an attempt myself, as I
think I have a quite clear idea of the problem.
Best Regards,
Ezio Melotti
cheers,
> Georg
>
___
python-committers mailing list
pyth
.
Best Regards,
Ezio Melotti
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers
-- Alexandre
It used to be set to True but IIRC at some point I changed it to be False.
Unless someone changed this intentionally, it's likely that the change
got lost when the repo got moved to HG.
Best Regards,
Ezio Melotti
___
python-committers m
zio after discussing it on IRC, on the basis that duplicate
bug should be sorted out in the tracker, but the majority here is in
favor. I’ll wait a bit for other opinions.
Clearly with -1 I meant "wishes -= 1", since now even this last one
should be fixed ;)
(http://hg.python.org/hoo
FI and he was the most active
contributor of the group.
Best Regards,
Ezio Melotti
cheers
Antoine.
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers
hon-dev channel on irc.freenode.net. There you can
get real-time updates about commits, new messages posted on the tracker,
the buildbots status, and you can also get in touch with other developers.
Best Regards,
Ezio Melotti
-- Meador
___
py
On Wed, Aug 31, 2011 at 8:44 PM, Ezio Melotti wrote:
>
>
>> 2) When a bug number (#\d+) is not in the first line of the commit
>> message, no message is sent. Is there a reason for this or is it a bug?
>> (Note: I’m not sure about this one, I may misremember.)
>>
t; distutils2 repo and send messages to Roundup when a bug number is detected.
>
>
It would be useful for the devguide repo too, now that we have a 'devguide'
component (and possibly for 'benchmarks' too, as you suggested on
#python-dev).
> Thanks in advance
&g
Hi,
On 03/08/2011 3.29, Pat Campbell wrote:
Hi Ezio:
Okay, and yes, please have Sandro submit a contributor agreement.
He should have sent it already yesterday morning, via fax.
Best Regards,
Ezio Melotti
Thanks,
Pat
___
python-committers
On 01/08/2011 17.00, R. David Murray wrote:
On Sun, 31 Jul 2011 19:53:00 +0300, Ezio Melotti wrote:
I would like to have Sandro added to the list of committers.
He has been very active on the bug tracker, doing triaging work and
contributing a number of patches.
He also reported more than 40
itted the contributor agreement yet but he will do it as
soon as he finds a printer/scanner/camera/fax.
Best Regards,
Ezio Melotti
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers
term feature branches.)
I'm not sure the mergediff extension can handle all this cases and, even
if it can, we need to adapt it to be used from the mail hook.
Best Regards,
Ezio Melotti
I have a script which kind of traverses all the local directories of
branches and does a hg pull;
On 05/04/2010 16.56, Michael Foord wrote:
Hello all,
I would like to propose Jean-Paul Calderone (exarkun) for commit access.
He is a core-twisted developer and a very experienced Python developer
with a passionate belief in good testing. He also regularly comments
the issue tracker. Twisted
78 matches
Mail list logo
