On Mon, May 1, 2017 at 3:32 PM, Christian Heimes wrote:
>
> 1) Should we try to move discussion back to BPO or are we fine with
> having major decisions just in Github PRs?
How will you do that? For Github, a PR and issue request ( an
equivalent of BPO issue) is same.
And we cannot disable revie
Support. :-)
On Tue, May 23, 2017 at 12:51 PM, Victor Stinner
wrote:
> Let me explain differently:
>
Also, liked reading Victor's email. :)
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python
Hello Python Committers,
I have been inactive (unsubscribed from all python.org) mailing list since
May 2017.
I had some study / other commitments that took too much time and I decided
to rest a little from volunteering efforts.
I just wanted to share this and I should perhaps inform active memb
Only committers can merge stuff. So, that would make a requirement that
reviewers (and @team-of-reviwers)should be core-dev / committers.
On Wed, Aug 2, 2017 at 2:47 PM, Steve Dower wrote:
> Should we seed the teams from the experts list?
>
>
>
> I have no strong opinion about core vs non-core
If you are going to use for CPython development, then reach out to Vinay
Sajip.
On Fri, Sep 1, 2017 at 7:09 AM, Paul Moore wrote:
> I've been trying out PyCharm recently, and looking through the
> archives here I see that some time back JetBrains provided us with a
> free open source license. Is
On Tue, Sep 5, 2017 at 6:10 PM, Mariatta Wijaya
wrote:
> Hi,
>
> The cherry picker bot has just been deployed to CPython repo, codenamed
> miss-islington.
>
> miss-islington made the very first backport PR for CPython and became a
> first time GitHub contributor: https://github.com/python/cpython
Congratulations, and Welcome Sanyam!.
Thank you, and keep up with your good work.
On Wed, Dec 6, 2017 at 1:43 PM, Victor Stinner
wrote:
> Hi,
>
> To recognize the good contributions of Sanyam Khurana, I gave him the
> bug triage permission on bugs.python.org. (In practice, Ezio gave him
> the
Hello Julien,
Welcome to this list, and good to meet you!
--
Senthil
On Sat, Dec 9, 2017 at 12:56 PM, Julien Palard via python-committers <
python-committers@python.org> wrote:
> Hi, python-committers!
>
> That's huge, for me, to receive this notification "Your now a core
> developer, congrat
+1
I have been following the discussions in python-dev and find his
contributions very productive.
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.pyt
Congrats, Łukasz. And Thank you, Ned, for managing the 3.6 and 3.7
Releases.
--
Senthil
On Sat, Jan 27, 2018 at 1:02 PM, Barry Warsaw wrote:
> As Ned just announced, Python 3.7 is very soon to enter beta 1 and thus
> feature freeze. I think we can all give Ned a huge round of applause for
>
Great idea. Definitely, +1.
On Mon, Feb 5, 2018 at 6:07 AM, Mariatta Wijaya
wrote:
> Hi,
>
> I will have some time in the next couple weeks to work on miss-islington.
> I'm thinking to work on this issue: https://github.com/
> python/miss-islington/issues/44
>
> The idea is to have miss-islingto
I like to seek one clarification.
I know git has author as well as committer. I am assuming that even if
miss-islington backports the PR, the author'ship of the patch is still
preserved.
Is that correct?
Thank you,
Senthil
On Mon, Feb 5, 2018 at 6:18 AM, Senthil Kumaran wrote:
> Gr
-1.
Registering my vote. I studied only the PEP and didn't follow the
debate/discussion.
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/ps
Welcome, Pablo!
Thank you, Victor, for enabling new developers!
Cheers,
Senthil
On Wed, Jun 20, 2018 at 8:30 AM, Pablo Galindo Salgado
wrote:
> Hi everyone,
>
> I would like to thank everyone for giving me their trust and allow me to
> be part of the team. Is really an honor
> to be part of s
On Wed, Jun 20, 2018 at 2:20 AM, Victor Stinner
wrote:
>
> > The result of the vote to to promote Pablo Salingo Salgado as core
> developer
> > after one week is positive: I declare that Pablo is now a core developer.
I couldn't participate this in vote. I just want to thank you introducing a
n
On Thu, Jul 12, 2018 at 7:57 AM, Guido van Rossum wrote:
I'll still be here, but I'm trying to let you all figure something out for
> yourselves. I'm tired, and need a very long break.
>
Thank you, Guido, for being the BDFL of Python. As the title goes, it is
for Life. :-)
I wouldn't worry abo
On Tue, Jul 17, 2018 at 7:02 PM, Barry Warsaw wrote:
>
> If you’ve read this far - thank you! Now for the big reveal. I think the
> Next BDFL should be… (drum roll)…
>
> Brett Cannon
>
> To summarize:
>
> * We retain a singular BDFL to lead Python
> * A Council is selected to serve as advisors
On Wed, Jul 18, 2018 at 9:38 AM, Antoine Pitrou wrote:
>
> Le 18/07/2018 à 18:36, Łukasz Langa a écrit :
> >
> >
> > A simple majority vote is wildly insufficient for this case. Python is a
> large project with many contributors and alienating maybe tens of them is
> not acceptable, especially if
On Wed, May 15, 2019 at 6:44 PM Ezio Melotti wrote:
>
> I share the same concerns:
1) the PEP contains several factual errors. I pointed this out during
> the core-sprints last year and more recently Berker pointed out some
> on GitHub: https://github.com/python/peps/pull/1013 ;
> 4) Berker is/
Thank you, Brett and others who helped.
Bug report: This template in the footer needs to be fixed:
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
On Wed, Jun 5, 2019 at 7:19 PM Brett Cannon wrote:
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> _
Congratulations, Dong-hee Na!
And thank you again, Victor, for constantly recognizing the contributions
of community members.
On Wed, Sep 4, 2019 at 9:10 AM Victor Stinner wrote:
> Hi,
>
> Dong-hee Na got the bug triage permission:
> https://github.com/python/core-workflow/issues/357
>
> The bu
Hi Guido,
> But I do want to emphasize that not everyone experiences the same dread
when requested to use a GitHub issue that you and Raymond seem to feel.
If I understand this correctly, it was not about the dread, but the overall
context already preserved in this discussion.
The feedback provid
Congratulations Łukasz on your first release as the release manager. Thank
you to all the contributors.
On Mon, Oct 14, 2019 at 3:26 PM Nick Coghlan wrote:
> Huzzah!
>
> Thank you to you and the rest of the release team for coordinating this,
> and to everyone that contributed changes and fixes
> As it turns out I was removed from the list of voters by the above
> script, without being asked, and would like to be added back again.
I support this, and I hope this can be rectified for this election
period itself.
Thank you,
Senthil
On Tue, Dec 10, 2019 at 12:52 PM M.-A. Lemburg wrote:
Welcome, Karthikeyan! Nice to have you here.
On Fri, Jan 3, 2020 at 9:21 PM Karthikeyan wrote:
> Thank you very much everyone for your kind words in the nomination
> thread, something I will cherish for a long time. I had a wonderful
> experience meeting the team during the sprints. Thanks Andre
Thanks a lot for this feature, Pablo.
Also, thanks in general for being a custodian of the build bots and CI.
On Mon, Jan 6, 2020 at 1:09 PM Pablo Galindo Salgado
wrote:
> ** Note: This message contains images and is better visualized in
> discourse:
> https://discuss.python.org/t/now-you-can-t
Hello Python-Committers,
In https://bugs.python.org/issue27657, I introduced a regression in a minor
release.
The original patch to parsing logic of URL, cleaned up a lot of corner
cases (https://github.com/python/cpython/pull/661) and I felt good about
the change.
However, the mistake was with th
Hi Łukasz ,
I wanted to push a revert in urlparse module in Python 3.8.2
I sent a note about this to python-committers, are you okay with this?
Thanks,
Senthil
On Mon, Feb 10, 2020 at 6:27 AM Senthil Kumaran wrote:
> Hello Python-Committers,
>
> In https://bugs.python.org/issu
it's a bit of a mess for 3.7 since that was way later in the
> release cadence with only 3.7.6 getting the change. I will let Ned decide
> here.
>
> - Ł
>
>
> On 10 Feb 2020, at 15:27, Senthil Kumaran wrote:
>
> Hello Python-Committers,
>
> In https://bugs
On Thu, Feb 13, 2020 at 1:57 AM Antoine Pitrou wrote:
>
>
> I would say it depends what the "revert" means:
> - revert to pre-bugfix behavior?
>
This.
Because the bug-fix was a bringing in backward-incompatible change that
certain users are not happy with.
https://github.com/mozilla/bleach/issue
Hi Łukasz,
As we have to a decision here, my vote is to revert the patch in 3.8.2 and
3.7.7
I have gone back-and-forth with this thinking, and it seems revert might
address some definite complaints we have got.
The problem is contained to single version, and users can upgrade to the
next one.
Tha
On Sun, Feb 16, 2020 at 2:20 AM Ned Deily wrote:
>
>
> For 3.9.0, I recommend we reconsider this change (temporarily reverting
> it) and consider whether an API change to accommodate the various use cases
> would be better
>
For 3.9. - I am ready to defend the patch even at the cost of the break
hil here. A slight behaviour change in 3.9 is
> fine, especially in an area where the "right" semantics are not
> immediately obvious. What we want to avoid is breaking behaviour
> changes in bugfix releases.
>
> Regards
>
> Antoine.
>
>
> Le 16/02/2020 à 13:
, Feb 16, 2020 at 12:13 PM Łukasz Langa wrote:
> OK, let's revert this for 3.8.2. I will make 3.8.2rc2 with this to
> highlight the revert and get some testing in.
>
> --
> Best regards,
> Łukasz Langa
>
> On 16 Feb 2020, at 19:31, Senthil Kumaran wrote:
>
>
Congratulations, Pablo!
Thank you for taking care of buildbots, and donning this new role.
On Tue, May 19, 2020 at 3:54 PM Barry Warsaw wrote:
> In light of the release of Python 3.9b1, let’s take a moment to celebrate
> all the great work that our Python 3.8 and 3.9 release manager Łukasz has
Welcome, Lysandros Nikolaou. Thanks for your work on PEG parsers.
On Tue, Jun 30, 2020 at 12:21 PM Brett Cannon wrote:
>
> ___
> python-committers mailing list -- python-committers@python.org
> To unsubscribe send an email to python-committers-le...
Hello Steering Council / Conduct Working Group,
I understand and appreciate sharing this with the python-committers list.
> Based on Code of Conduct violations in your recent mailing list posts,
and under the recommendation of the Code of Conduct Working Group, the
Python Steering Council has vot
I am sad about this turn of the event too, and I hope we as Python
developers try to avoid this in future.
The only think Stefan mentions directly in the forwarded email is,
> Having a shared understanding of what constitutes politeness is
> important and eliminates all sources of friction that s
On Fri, Oct 16, 2020 at 12:26 PM Brett Cannon wrote:
>
> On Fri, Oct 16, 2020 at 11:58 AM Pablo Galindo Salgado <
> pablog...@gmail.com> wrote:
>
>> > We should simply mark the github actions "Tests / Ubuntu" CI as
>> required.
>>
>> +1 I completely agree with everything Gregory said.
>>
>
> +1 f
I had formed my opinion at Barry's email very early. I favor not
backporting too. This is a new class and we cannot control people
expectations.
We are going to have yearly release cycles that is another reason not to
backport this, and only move forward.
On Mon, Oct 26, 2020 at 12:34 PM Brandt B
Congratulations, Batuhan.
Was happy to see you during core sprints. For those of us who don't know
much about you, please share something about yourself.
Thank you,
Senthil
On Tue, Nov 10, 2020 at 1:44 PM Kyle Stanley wrote:
> Welcome to the core dev team, Batuhan!
>
> On Mon, Nov 9, 2020 at
Congratulations to 2021 Python Steering Council. :)
Ethan Furman wrote:
>
> Now please hurry up and accept the pattern-matching PEPs. ;-)
>
Yup. :) It's almost like the committee gave the recommendation to itself,
and got more time to discuss it.
--
Senthil
___
Hi Jack,
If it is a security issue, then secur...@python.org would be the list -
https://www.python.org/dev/security/
Thank you,
Senthil
On Mon, Dec 28, 2020 at 12:45 PM Jack Jansen wrote:
> I have a security question that I’d like to drop in the Python committers
> community, but I noticed th
Hi Pablo,
Looks like alpha 5 was scheduled for today. I am willing to take care of
this issue - https://bugs.python.org/issue42967
The patch is reasonable, but the changes are backwards incompatible.
Since it is with an underlying parsing library, the decision here is tricky
one way or the other.
Hello Python Developers,
I notice TLS tests failing in the ssl test suite in master, 3.9 and
3.8 branches.
https://github.com/python/cpython/runs/2018191733
Is it to do with infrastructure, certificate? I am unable to determine
it exactly.
The failure is observed upon merge to master. or with 3.
On Tue, Mar 2, 2021 at 8:29 PM Gregory P. Smith wrote:
>
> For lack of better things to do with that...
> https://bugs.python.org/issue43382 filed to track it.
Actually, that turned out to be useful. Thank you!
The discussion with the default minimal level TLS, and way it is
configured in distr
On Wed, Mar 3, 2021 at 8:08 AM Christian Heimes wrote:
> PEP 644 (not approved yet) and a soon-to-be-published PEP will hopefully
> get rid of the problem once and for all. PEP 644 removes support for
> OpenSSL < 1.1 and the new PEP will remove support for TLS 1.0 and 1.1
> from stdlib.
>
> https
On Tue, Mar 16, 2021 at 9:42 AM Christian Heimes wrote:
> GPG signatures are
> problematic because GPG is awful.
What is the problem here? Most of the verification for external
downloads, at the moment, seems to be via GPG.
> Sigstore [2] might become an alternative in the future.
TIL. Seems ve
I have worked with Ken, and I admire his attitude towards many things when
dealing with bugs and feedback in Python development.
Congrats Ken!
--
Senthil
On Sun, Apr 11, 2021 at 10:49 AM Carol Willing wrote:
> Congrats Ken! You've been doing great work. Looking forward to continuing
> to wor
Thanks for posting this here.
I might have missed this vote if it were not posted here. I rarely visit
discourse. Should we consider forwarding the first post of "committers"
category to this mailing list?
--
Senthil
On Thu, Apr 29, 2021 at 01:55:25PM -0700, Brett Cannon wrote:
> https://discuss
On Fri, Apr 30, 2021 at 11:12:55AM -0700, Brett Cannon wrote:
> On Thu, Apr 29, 2021 at 3:54 PM Senthil Kumaran wrote:
>
> Thanks for posting this here.
>
> I might have missed this vote if it were not posted here. I rarely visit
> discourse. Should we consider fo
On Fri, May 7, 2021 at 10:39 AM Dong-hee Na wrote:
Erlend improved the sqlite3 module for the recent period and he shows
> notable knowledge about sqlite3. So I believe that his contribution will
> enhance the CPython project and I think that he is well deserved to get
> triage permission.
> I am
On Wed, May 12, 2021 at 07:22:52AM -0700, Guido van Rossum wrote:
> I recall seeing this for other recent issues as well. Did some piece of
> automation recently break? (Could it have to do with the master->main move?)
Looks like the link is broken only for "main" branch.
It works for 3.10 (and po
Hello Core Dev,
I find a need for a core-dev chat service, wherein I could engage in
some quick effervescent conversations.
It is like a team chat, that is popular with remote work these days.
We even seem to have used Zoom Chat yesterday!
* I know #python-dev in IRC exists, but it is mostly a c
On Thu, May 13, 2021 at 04:53:08PM -0700, Guido van Rossum wrote:
> I’ve found Gitter works well. I’d use that, assuming it was only open to core
> devs and invitees.
Thanks! I interpret this as
a) Yes to a need for chat-service for core-dev.
b) Add Gitter to the list of options to consider too.
On Thu, May 13, 2021 at 05:17:33PM -0700, Gregory P. Smith wrote:
> We already have https://python.zulipchat.com/ setup. https://mail.python.org/
> pipermail/python-dev/2018-April/152826.html
Is it fair to say that it didn't take off as well as we intended?
Even discuss.python.org beat that take-
On Fri, May 14, 2021 at 09:03:05AM +0200, Antoine Pitrou wrote:
> Well, the more you create chat services for a single purpose, the less
> you're likely to actually find a community there. Why do you want to use
> Gitter if Zulip and IRC already exist?
The goal is not the tool, but the community
On Fri, May 14, 2021 at 09:36:52AM +0200, Antoine Pitrou wrote:
> #python-dev on IRC has been wildly successful until perhaps 2015.
> Personally, I would have no problem using IRC if wanted to connect to a chat
> for CPython at all.
I know, it was useful, and #python is still. The bot, github, bui
On Fri, May 14, 2021 at 12:28:00PM +0200, Victor Stinner wrote:
>
> The bugs.python.org and buildbot notifications are useful to me and I
> don't feel annoyed by them. But GitHub review are hard to use: only
> the user name and the PR number are given: PR title and comment
> content are not provid
On Fri, May 14, 2021 at 11:07:12AM -0700, Brett Cannon wrote:
> You could launch a poll on discuss.python.org and see if there's a clear
> winner.
Yes, after hearing some opinions, I plan to do that. Right now, I guess
the choices I am thinking are
- No, I am not interested in Chat.
- Focus on #
On Fri, May 14, 2021 at 11:28:48AM -0700, Mariatta wrote:
> I hope we can properly evaluate how the next chosen chatting platform
> can be used more effectively.
I agree. The proposal is like choice of Github. We don't self-host, but
if identify something that will work for us (provided there is
On Fri, May 14, 2021 at 06:30:33PM +, Jason R. Coombs wrote:
> Would be delighted if there was a preferred platform for chat and that
> platform
> be documented (and allowed to change as solutions and the community evolves).
This resonates well with me. Especially as I use _ these chat platfo
On Fri, May 14, 2021 at 09:21:14PM +0200, Marc-Andre Lemburg wrote:
> Wouldn't it make more sense to run a matrix.org server which then
> connects and bridges across all those channels ?
>
> https://matrix.org/bridges/
>
> People could then continue to use their preferred platform,
> without losi
On Fri, May 14, 2021 at 08:53:13PM +0100, Paul Moore wrote:
> The problem with this, I think, is that my choice would be
>
> * Whichever one people actually used
That's self-referencing, and unsolvable.
> In other words, this isn't a technology problem, it's a people
> problem.
Both. I didn't
On Sat, May 15, 2021 at 11:13:48AM +0900, Dong-hee Na wrote:
> So I'm also a supporter of new communication tools.
I agree with everything you've mentioned, Dong-hee. Need for good
tool/system that addressed our evolving needs was one of the driver of
this conversation.
Thanks!
__
On Sat, May 15, 2021 at 04:16:20PM +0200, Antoine Pitrou wrote:
> You still haven't explained why e.g. Zulip (which has a modern Web UI, a
> very well-thought threading mechanism, several clients, many integrations,
> is widely used, and is open source), doesn't « address our evolving needs ».
- Z
On Sat, May 15, 2021 at 05:17:03PM +0200, Antoine Pitrou wrote:
>
> Le 15/05/2021 à 17:11, Dong-hee Na a écrit :
> >
> > So I agree with you and my suggestion may not be an objective perspective.
> > But I think that if we decide to choose to adopt new communication
> > tools, I think that we can
Antoine Pitrou wrote:
> > I'll ask the question again: what are the « evolving needs » that are
> not addressed by Zulip, but would be addressed by *another* chat system?
I don't understand this question, and lost the context too if it was addressed
to me.
The fact is, Zulip simply isn't used b
Eric V. Smith wrote:
> If the intent of this new core-dev chat is just a social "how are you
> doing" sort of thing, then I think Zulip (or most anything else) would
> work fine.
What would be _social_ for python-dev? :) I assume it will mostly be around
technical topics.
The social nature obs
On Sat, May 15, 2021 at 06:01:36PM +0100, Paul Moore wrote:
> I see a general interest in *having* some sort of community chat, but
> no real plan on how to get a critical mass of people on a chat system.
So, I see you recognize the general interest too. Next step will
figuring out what to do, an
On Sat, May 15, 2021 at 09:16:33AM -0700, Brett Cannon wrote:
> As a data point for where newer language communities have ended up, Rust is on
> Discord and Zulip.
I hopped in to study their usage for last 3 days. I wanted to find out
how open source communities are actively using Zulip.
* Zulip
Senthil Kumaran wrote:
> Hello Core Dev,
> I find a need for a core-dev chat service, wherein I could engage in
> some quick effervescent conversations.
...
> Does anyone else feel the need? Should we explore any? My thoughts and
> options are
...
> If you think that chatting
On Sat, May 22, 2021 at 01:54:23PM -0700, Guido van Rossum wrote:
> 2. I can handle Discord just fine nowadays but *please* don't combine this
> with
> the Python Discord server.
This was expressed by other core-devs as well.
> 8. I would want a purely *social* chat that is *closed* to non-cor
On Sat, May 22, 2021 at 02:50:23PM -0700, Guido van Rossum wrote:
> Wait, is there already a vote somewhere?
Not yet. I will create one in discuss.python.org
I had summarized our discussion and shared what would be the questions
and voting options here.
https://mail.python.org/archives/list/pyt
Please vote on this topic of "Core-dev" chat choice.
https://discuss.python.org/t/vote-on-core-dev-chat-choice/8870
Thank you,
Senthil
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-l
On Mon, May 24, 2021 at 12:16:22PM +0200, Victor Stinner wrote:
> Your poll has a choice: "IRC channel other than #python-dev".
>
> FYI buildbot notifications already moved from #python-dev to
> #python-dev-notifs.
>
> I created a PR to move GitHub notifications there as well:
> https://github.c
a related note, since the start of these discussions, multiple
changes resulted in #python-dev on IRC (libera.chat) picking up on
human interaction. That's a great development. IRC is forever!
Thank you,
Senthil
On Mon, May 24, 2021 at 6:12 AM Senthil Kumaran wrote:
>
> On Mon, May
On Mon, Jul 12, 2021 at 10:42:45AM -0500, Ewa Jodlowska wrote:
> Just to circle back, we have officially contracted with Łukasz Langa to be the
> first CPython Developer-in-Residence!
Congratulations, Łukasz!
I read your blog post in your decision, and it is great that you are
stepping in contri
On Tue, Oct 05, 2021 at 09:46:44AM -0700, Mariatta wrote:
>
> I do have the ability to add/remove hacktoberfest topic myself, so if we're
> okay with this, I can go ahead and do it. I will also remove the topic once
> the
> month ended.
+1 to this initiative.
--
Senthil
__
Thank you, Barry and thank you all volunteers who participated.
Congrats to the new SC members.
--
Senthil
On Sun, Dec 19, 2021 at 01:55:27PM -0800, Barry Warsaw wrote:
> My deepest thanks to everyone who voted for me, and my heartfelt
> congratulations and support to all the members of the 202
On Thu, Feb 17, 2022 at 10:23:47AM -0800, Ethan Furman wrote:
> On 2/17/22 10:11 AM, Gregory P. Smith wrote:
>
> >> - Subscriptions may expire for lack of activity, but resubscribing is
> >> welcomed.
> >
> > This does not mean we /need/ to expel people due to inactivity. Lurking is
> > one met
I had to reinstall my OS recently and I checked out pristine copies of
trunk,py3k,release26-maint,release31-maint.
While svnmerge.py init on release26-maint and release31-maint worked
fine and I was able to merge a revision to release26-maint.
On py3k, the svn init gave the following problem.
$
On Tue, Mar 23, 2010 at 3:57 PM, Victor Stinner
wrote:
> Why are you using svn init? It was already done in all branches.
I had this understanding that, while using svnmerge.py you might to do
one-time operation on svnmerge.py init on local repo and then do the
svnmerge.py merge -r xxx
http://ww
On Mon, Jun 28, 2010 at 01:31:38PM -0400, Jesse Noller wrote:
> My apologies everyone. Apparently my three year old knows how to
> work the mail app on my iPhone.
Wow!. The youngest Python Core developer. :)
--
Senthil
If a guru falls in the forest with no one to hear him, was he really a
guru
On Tue, Jun 29, 2010 at 3:28 AM, "Martin v. Löwis" wrote:
>
> The ones I want to get done are PEPs 382 and 384.
Just to have the direct information on these PEPs inline.
PEP 382 - Namespace Packages
http://www.python.org/dev/peps/pep-0382/
PEP 383 - Definition of Stable ABI
http://www.python.or
On Sun, Jul 18, 2010 at 11:09:43AM +1000, Nick Coghlan wrote:
> I'd like to propose Terry Reedy as a new comitter.
>
> He has been contributing to Python via the tracker, c.l.p, python-dev
> and python-ideas for years and has recently requested commit
> privileges in order to work on IDLE. I think
Hi Tarek,
On Tue, Jul 27, 2010 at 12:36:12PM +0200, Tarek Ziadé wrote:
> Depending on your definition of core, none. He works on Distutils2 and
> helps me (and other) in the tracker.
I support Antoine here. The core may not just mean the CPython
interpreter, but the stdlib module too.
Simple pat
On Tue, Aug 3, 2010 at 9:32 PM, Michael Foord wrote:
> Barry Warsaw is Wary Bra Wars, whilst Steve Holden is Eleventh Sod. Mark
> Dickinson is Kid Conman Risk, whilst Raymond Hettinger is A Trendy
> Mothering. Hmm.. the alter egos of our Python super heroes needs work
I would just imagine that Ra
On Mon, Nov 08, 2010 at 11:55:39AM +0100, Łukasz Langa wrote:
> Even if that commit hook prevents a single wrong commit a year, it's
> worth it. As unpaid volunteers, we don't have time for hunting the
> same mistakes twice.
For common mistakes, there are commit hooks which prevent you from
commit
On Tue, Nov 16, 2010 at 10:25 PM, Steve Holden wrote:
>
> Any why wouldn't the py3k branch now be trunk?
If you meant, why would't the py3k branch be renamed to trunk, then I
think, it was do with svn properties and tracking of merges.
We use svnmerge to backport py3k to release31-maint and
relea
On Sun, Dec 05, 2010 at 12:16:48PM +0100, Georg Brandl wrote:
> I wonder if it's still necessary to provide .tar.bz2 and .tgz source
> tarballs.
Yes, it is necessary. People sometimes just expect it from an Open
Source project. (At least, when someone is going to try it for the
first time)
> If
+1.
We will have another OS X developer.
On Sun, Jan 9, 2011 at 8:52 AM, Raymond Hettinger
wrote:
> +1
>
> On Jan 8, 2011, at 3:50 PM, Antoine Pitrou wrote:
>
>>
>> Hello,
>>
>> Based on his work to diagnose and fix many issues related to OS X and/or
>> IDLE/tk, I would like to propose that we g
On Sun, Feb 13, 2011 at 12:22:46PM +, Vinay Sajip wrote:
> Here's the patch:
>
> https://gist.github.com/824644
>
I think you missed the rc3 freeze email. :)
--
Senthil
___
python-committers mailing list
python-committers@python.org
http://mail.p
On Sun, Feb 13, 2011 at 9:44 PM, Michael Foord wrote:
> On 13/02/2011 13:42, Senthil Kumaran wrote:
>>
>> On Sun, Feb 13, 2011 at 12:22:46PM +, Vinay Sajip wrote:
>>>
>>> Here's the patch:
>>>
>>> https://gist.github.com/824644
>>&
On Sun, Apr 3, 2011 at 11:17 PM, Antoine Pitrou wrote:
> I'd like to propose giving committer rights to Nadeem Vawda.
+1 to this proposal. Please ensure that Nadeem Vawda is "interested" too.
--
Senthil
___
python-committers mailing list
python-commi
ser: Senthil Kumaran
date: Wed Apr 06 14:41:42 2011 +0800
summary:
hg pull/merge - Changes to accomodate.
files:
Lib/test/test_datetime.py | 7 +++
Modules/datetimemodule.c | 15 ---
2 files changed, 15 insertions(+), 7 deletions(-)
diff --git a/Lib/t
Hi Barry,
On Fri, May 20, 2011 at 06:32:29PM -0400, Barry Warsaw wrote:
> I did. Right now I'm blocked on a test failure for test_urllib2, but it's
> failing in both the hg and svn branches, so at least it wasn't a result of a
I assume, you managed to resolve it as I saw the release mail from
yo
+1 from me as well.
It would be good to request new committers to write an introductory
mail about themselves.
Thanks,
Senthil
On Mon, Aug 01, 2011 at 11:10:15AM -0700, Brett Cannon wrote:
> I have also interacted with him and been happy with the outcome, so +1 from me
> as well.
>
> That seem
On Sat, Oct 22, 2011 at 11:13:25AM +1000, Nick Coghlan wrote:
> >
> > Petri Lehtinen has been an active contributor for some time, he has been
> > quite receptive to reviews and we have committed a dozen of his patches.
> > Do you think it is time to offer him commit rights?
>
> +1 from me - I was
I think, there is something wrong with state of hg.python.org at the moment.
On a fresh clone from hg.python.org
$hg clone ssh://h...@hg.python.org/cpython cpython
If I do, hg branches, the 3.2 is shown as inactive. Did something
change recently?
(env27)bash-3.2$ hg branches
default
1 - 100 of 140 matches
Mail list logo
