On Tue, 02 May 2017 09:36:02 +0200, "M.-A. Lemburg" wrote:
> On 02.05.2017 04:25, Nick Coghlan wrote:
> > On 2 May 2017 at 08:32, Christian Heimes wrote:
> >> This brings me to my questions
> >>
> >> 1) Should we try to move discussion back to BPO or are we fine with
> >> having major decisions j
On Thu, 04 May 2017 17:44:46 -, Brett Cannon wrote:
> (And just so I can claim I stated this publicly at some point; our Roundup
> installation I think runs on Python 2.6 and Roundup itself has not been
> ported to Python 3, so I don't know what we want to do if Roundup doesn't
> make the swit
On Wed, 17 May 2017 11:35:29 -0700, Mariatta Wijaya
wrote:
> It's possible, but remember not all PRs have bpo-issue, eg those with
> trivial label.
> In that case, what should the backport branch be?
> So we might end up with two backport branch name patterns, eg
> `backport-bpo--` and `backp
+1
--David
___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/
On Thu, 15 Jun 2017 13:31:39 +1000, Nick Coghlan wrote:
> On 15 June 2017 at 00:40, Victor Stinner wrote:
> > So I would like to set a new rule: if I'm unable to fix buildbots
> > failures caused by a recent change quickly (say, in less than 2
> > hours), I propose to revert the change.
>
> I'm
On Wed, 21 Jun 2017 10:02:58 -0700, Mariatta Wijaya
wrote:
> Yes, for that PR, scroll down and click the "View Details" button.
> Click the Details link next to bedevere/issue number status check.
> It will take you to the issue in bpo.
Note that this will only exist if the PR is still open (not
On Wed, 21 Jun 2017 13:37:22 -0700, Mariatta Wijaya
wrote:
> PR 2304 is merged. "View Details" still exists (scroll all the way down).
>
> When the PR is not yet merged (e.g.
> https://github.com/python/cpython/pull/2316), the UI looks different.
> Click 'Show all checks' to get the link back to
On Sat, 24 Jun 2017 00:33:13 -, Brett Cannon wrote:
> On Fri, 23 Jun 2017 at 09:28 R. David Murray wrote:
>
> > On Wed, 21 Jun 2017 13:37:22 -0700, Mariatta Wijaya <
> > [email protected]> wrote:
> > > PR 2304 is merged. "View Details&
On Tue, 18 Jul 2017 12:24:13 +0200, Victor Stinner
wrote:
> I'm just not unconfortable with the fact that an approval is kept even
> if the PR is modified after the review :-/ I would expect a list a
> notice "changed modified after the review" or something like that. At
> least, for my own revie
On Tue, 18 Jul 2017 23:13:41 -, Brett Cannon wrote:
> Do realize that setting is part of requiring a review for pull requests:
> https://help.github.com/articles/enabling-required-reviews-for-pull-requests/.
> So in order to get this we would require all PRs, core dev or not, to
> receive an a
I haven't actually heard back from him yet since I just emailed him,
but I've never had anyone turn down triage privs :)
The trigger was that I closed two issues this week that he comment on
that it would have been nice if he had been able to just close himself.
I've looked at some of his other tr
A link to a possibly-interesting-in-this-context project was just posted
to the pmem mailing list:
https://arrow.apache.org/
This is a standard for communicating data structures between processes
with zero-copy semantics, and is backed by the person who created Python
Pandas. I thought Davin
On Fri, 06 Oct 2017 09:09:01 -0700, Mariatta Wijaya
wrote:
> The windows team is notified because the PR includes changes to PCBuild/*
If you get a review request that says your review was requested "as a
code owner", then it was an auto-request, it wasn't actually requested
by the person named
On Mon, 06 Nov 2017 11:46:48 +1000, Nick Coghlan wrote:
> On 6 November 2017 at 02:02, Yury Selivanov wrote:
> > On Fri, Nov 3, 2017 at 11:30 PM, Nick Coghlan wrote:
> >> The current lack of DeprecationWarnings in 3.6 is a fairly major
> >> oversight/bug, though:
> >
> > There's no oversight. W
On Mon, 06 Nov 2017 12:51:45 -0600, Neil Schemenauer
wrote:
> Another idea is to have venv to turn them on by default or, based on
> a command-line option, do it. Or, maybe the unit testing frameworks
> should turn on the warnings when they run.
Unit test frameworks, including at least unittest
On Mon, 06 Nov 2017 13:25:09 -0600, Neil Schemenauer
wrote:
> On 2017-11-06, R. David Murray wrote:
> > I'm curious which ones you are seeing it in? It could be we are
> > operating in different problem spaces :)
>
> In the last few months: Pillow, docutils, dateu
On Mon, 20 Nov 2017 18:54:50 +0100, Victor Stinner
wrote:
> I identified some active contributors and I would like to offer them
> to get the "bug triage" permission. What's the requirements to give
> such permissions to someone?
Currently it is "someone with the power to do it decides to give i
On Wed, 06 Dec 2017 08:43:56 -0800, Guido van Rossum wrote:
> I think I figured it out -- I invited him to the python org on GitHub.
> Anything else?
He needs to subscribe to this mailing list, and the developers.rst in
the devguide repo should get an update.
That's all I can think of, since ssh
On Wed, 06 Dec 2017 18:11:44 +0100, Victor Stinner
wrote:
> Ok, thanks Ezio and David. I completed my list:
> https://github.com/vstinner/cpython_core_tutorial/blob/master/core_developer.rst#bug-tracker
s/loose/lose/
I would say your list comprises the skills for the "ideal triager" rather
than
On Thu, 07 Dec 2017 13:00:31 -0500, Barry Warsaw wrote:
> Brett and I want to promote this more widely within the Python
> community as the âofficial Python Docker imageâ that projects can use
> in their own testing environments, or base their own images on it. We
> wanted to give you guys a
On Sat, 09 Dec 2017 14:12:52 +0100, Victor Stinner
wrote:
> I asked them to ask me to double check before merging a pull request
> (Julien) or closing a bug (Cheryl and Sanyam).
When I have promoted people to triage in the past I have not had them
check with me before making changes, but instead
On Mon, 11 Dec 2017 18:14:41 +, Paul Moore wrote:
> On 11 December 2017 at 18:03, Donald Stufft wrote:
> > So yea, itâs not as good as 2FA only everywhere, but the specific
> > circumstances around these specific credentials makes it a reasonable
> > usability trade off to allow them.
>
>
On Mon, 11 Dec 2017 14:52:54 -0500, "R. David Murray"
wrote:
> Indeed. If 2fa is required for contribution to CPython, I'll stop
> contributing. Granted, I haven't done many merges lately, but a few
> is a bigger number than zero :)
And in case you think this me
On Mon, 11 Dec 2017 14:56:21 -0500, Donald Stufft wrote:
>
> > On Dec 11, 2017, at 2:52 PM, R. David Murray wrote:
> >
> > If 2fa is required for contribution to CPython, I'll stop
> > contributing.
>
> Iâm curious why? I have it on and 99% of the
On Wed, 31 Jan 2018 03:17:47 -0500, Ned Deily wrote:
> in not more than 24 hours from now. If you wish, feel free to merge
> new commits into the master branch for release in 3.8, with the
> understanding that any also destined for 3.7.0 will need to be
> cherrypicked after the 3.7 branch is avai
At Yuri's request I've given Elvis triage privileges on the tracker.
I don't anticipate any objections, given the work he's done on
What's New and other things.
--David
___
python-committers mailing list
[email protected]
https://mail.python.o
On Fri, 3 Jul 2009 at 00:58, Anthony Baxter wrote:
Speaking as a past release manager, the reason that things like that didn't
get merged is because... drumroll... no-one merged them.
It's another tree to checkout and patch. Personally, I was always of the
belief that if someone wanted to fix doc
On Fri, 3 Jul 2009 at 02:13, Anthony Baxter wrote:
The particulars of the revision control system don't matter as much as the
discipline of teaching people to commit fixes. Right now, we have 2.6.x,
3.0.x and 3.1.x.
No, we have 2.7, 2.6, 3.2, and 3.1.
Using svnmerge to commit to three branches
On Thu, 2 Jul 2009 at 11:43, Brett Cannon wrote:
On Thu, Jul 2, 2009 at 11:42, Barry Warsaw wrote:
On Jul 2, 2009, at 2:29 PM, Anthony Baxter wrote:
I think Barry should totally cut a completely pointless 3.0.2 release. We
can call it the "homage to 1.6" release.
We can code name it "Her
On Thu, 2 Jul 2009 at 18:26, Barry Warsaw wrote:
On Jul 2, 2009, at 6:23 PM, Brett Cannon wrote:
Sounds like general consensus that 3.0.2 isn't worth it. Is an announcement
on c.l.p.a and something on www.python.org enough to get the word out that
3.0.2 is not going to happen and 3.0 users sho
Jesus Cea wrote:
Georg Brandl wrote:
I think this should be reverted -- the support code is not for the
bsddb module, but for building the dbm module with bsddb.
I pretend to ask for re-inclusion of BerkeleyDB in Python 3.x branch in
the future (maybe around christmas), now that it is under co
On Sat, 11 Jul 2009 at 02:41, Jesus Cea wrote:
R. David Murray wrote:
It seems to me (though I admit I haven't been watching closely recently)
that the buildbots still report bsddb errors on trunk on a fairly regular
basis. If I'm not imagining things is there any chance you could t
On Thu, 13 Aug 2009 at 09:00, Brett Cannon wrote:
Is this an alpha or beta cut for 3.1.1? I have a crasher fix I plan to
commit later today.
It's an RC.
--David
___
python-committers mailing list
[email protected]
http://mail.python.org/ma
On Thu, 13 Aug 2009 at 15:03, Jerry Seutter wrote:
On Thu, Aug 13, 2009 at 1:44 PM, Brett Cannon wrote:
File "/Users/brett/.slash/python/lib/python2.6/encodings/mac_roman.py",
line 12, in encode
return codecs.charmap_encode(input,errors,encoding_table)
UnicodeEncodeError: 'charmap' codec
On Sun, 13 Sep 2009 at 13:15, Brett Cannon wrote:
On Sun, Sep 13, 2009 at 09:07, Gregory P. Smith wrote:
Thanks. ??One reason this happens is that our NEWS file is very
difficult to navigate. ??svnmerge rarely works on it because the
context is often different in the branch file but figuring ou
On Mon, 14 Sep 2009 at 12:40, Georg Brandl wrote:
Yes, but still: in many cases they are very similar.
Plus, it's hard to auto-add a NEWS entry from a commit message (because
you need to determine the right section), while it's easy to pre-fill
the commit message from a NEWS diff.
But the prob
On Tue, 13 Oct 2009 at 12:57, Barry Warsaw wrote:
On Oct 13, 2009, at 11:16 AM, Tarek Ziad? wrote:
I still need to do some more tests, I didn't have time to try the
various projects under win32.
It's planned to night.
The tests are consisting of compiling and insatling a dozain of
projects on l
On Tue, 02 Mar 2010 15:41:45 +0100, Dirkjan Ochtman wrote:
> On Tue, Mar 2, 2010 at 15:17, Barry Warsaw wrote:
> > We really need to move to a dvcs for development sooner rather than later.
> > It's been a year since the decision was made. Â I understand that it will
> > suck
> > for Windows dev
I've also asked Brian Curtain to test the extension and he said he would.
(He's been doing bug triage, and testing and writing a bunch of windows
patches...I think he should be considered for commit access in the not
too distant future.)
--David
___
pyth
On Wed, 03 Mar 2010 22:32:24 +, Vinay Sajip wrote:
> I've installed Keychain and invoked it in my .bashrc, and whenever I open a
> terminal session, it tells me that it found an existing ssh-agent and the
> SSH_AUTH_SOCK and SSH_AGENT_PID seem to be correct. Yet, I get prompted for
> the
> pa
is a one-time operation (i.e. only when the
> branch is originally created, not when each developer creates a local
> checkout for the branch)."
+1. I was bitten by this when I first started, and I think your
proposed wording explains it well and would have kept
On Wed, 07 Apr 2010 12:54:51 +0100, Michael Foord
wrote:
>On 07/04/2010 11:30, anatoly techtonik wrote:
>> There is still a serious regression in zipfile module:
>> http://bugs.python.org/issue6090
>>
>> And I would really like to see my issue with difflib tabs committed: =/
>> http://bugs.python
pert for
ftplib.)
--
R. David Murray www.bitdance.com
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
her.)
--
R. David Murray www.bitdance.com
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
d
> attention.
>
> Any objections or comments?
+1
He's also expressed interest in memoryviews, which I suspect
will make Antoine, at least, happy :)
--
R. David Murray www.bitdance.com
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
ut the commit process (everyone
does) and perhaps the development environment/tools. I'm sure the
#python-dev regulars would be glad to help out with those questions
as well, if he visits there.
--
R. David Murray www.bitdance.com
__
On Mon, 08 Nov 2010 14:24:57 -0500, Terry Reedy wrote:
> A request to email my password again, in case it was automatically
> changed, also failed.
Are you sure you are using the email address under which you
are subscribed?
--
R. David
On Wed, 01 Dec 2010 14:53:21 -0500, Terry Reedy wrote:
> I would like to commit a couple of new feature patches in the next
> couple of days for #9299 (if no one else does it) and #10534 (working on
> that). It appears to be somewhat customary to follow such patches with
> 3.1/2.7 blocks, but
On Wed, 01 Dec 2010 22:23:18 +0100, Jesus Cea wrote:
> On 01/12/10 21:48, R. David Murray wrote:
> > My understanding of the current status of svnmerge block is that
> > you should use it if it helps you and not worry about it otherwise.
> > Georg and I and some others find i
On Thu, 02 Dec 2010 02:19:25 +0100, wrote:
> Le 01/12/2010 21:48, R. David Murray a écrit :
> > My understanding of the current status of svnmerge block is that
> > you should use it if it helps you and not worry about it otherwise.
> > Georg and I and some others find it us
Gah, I just realized that I committed something and I haven't seen
Georg's unfreeze message yet.
It was wrong anyway, so I reverted it.
--David
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/pytho
working, whereas if we put the patch in
but there turn out to be edge case bugs, we can fix those bugs in 3.2.1...
If the module weren't already broken for most real-world purposes I'd
no question want to wait. As it is I'm on the fence.
--
R. David M
th down-porting.
As Nick pointed it, it is much worse to forget to forward port a patch
than to forget to back port it. We have had a few of the former even with
our current workflow, and it is really embarrassing when it happens[*].
--
R. David Murray www.
ood. And even after
I'm going to need help...I tried using bzr for email6 and I *still*
don't understand how to use it properly. Of course, nobody had written
a best practices guide for me for my project, which is why I'm joining
the
yself, but he is
someone I have on my mental list as "probable future committer" based
on the activity I've noticed. So if Antoine says it's time, I say +1.
--
R. David Murray www.bitdance.com
___
ly signable agreement
and/or adding "posting a patch to this tracker means you have the right
to contribute it and you do contribute it" language to the tracker?
--
R. David Murray www.bitdance.com
__
at this rarely happens in practice. At least, it rarely happens
that the PSF has the form in hand and acknowledged prior to the first
significant checkin.
--
R. David Murray http://www.bitdance.com
___
python-committers mailing list
python-comm
I think it happened on
python-dev rather than here, though. (Since I didn't have any branches
at the time I didn't pay much attention to it.) I'm pretty sure it
was mentioned again just pre-conversion, but I don't think any details
were given at that time.
--
R
On Fri, 20 May 2011 21:09:02 -0400, Barry Warsaw wrote:
> I asked around on #python-dev and it was suggested that I add some entries
> into .hgeol, which I've done:
>
> Doc/make.bat = CRLF
> Tools/buildbot/*.bat = CRLF
> Tools/msi/merge.py = CRLF
> PC/VS7.1/*.bat = CRLF
> PC/VS8.0/*.bat = CRLF
>
committing anything right now because it just isn't clear to me
how all of this is working, so for me it's as if we have a freeze just
like we had with our SVN procedures.
(The 2.7 branch, on the other hand, looks as I would expect, with
the section header referring to 2.7.3.)
On Wed, 08 Jun 2011 21:29:21 -0700, Ned Deily wrote:
>
> On Jun 8, 2011, at 18:43 , R. David Murray wrote:
>
> > I am completely confused by the state of the 3.2 branch. My understanding
> > is that RC1 has been released, that RC2 is coming soon, and that Georg
> >
On Thu, 09 Jun 2011 19:46:25 +0200, Georg Brandl wrote:
> On 06/09/11 17:42, R. David Murray wrote:
> > On Wed, 08 Jun 2011 21:29:21 -0700, Ned Deily wrote:
> >>
> >> On Jun 8, 2011, at 18:43 , R. David Murray wrote:
> >>
> >> > I am complet
on't think we need to have any worry about
his going crazy with code commits...he's very aware of the need
to be conservative and get reviews.
Ezio, are you volunteering to be his mentor? If so, then definitely +1.
--
R. David Murray http://www.bitdance.com
__
I just tried to merge a change from 3.2 to default and found an unexpected
file being merged. Looking at the graph, it *looks* like Sandro copied a
change to default instead of merging it, even though his commit comment
says merge. That would be fine, I'd just do a null merge...except that
the fi
On Fri, 06 Apr 2012 09:57:29 +0200, Georg Brandl wrote:
> Am 06.04.2012 04:44, schrieb R. David Murray:
> > I just tried to merge a change from 3.2 to default and found an unexpected
> > file being merged. Looking at the graph, it *looks* like Sandro copied a
> > change
On Mon, 23 Apr 2012 00:14:58 +0200, [email protected] wrote:
>
> Zitat von Philip Jenvey :
>
> > On Apr 22, 2012, at 10:26 AM, Martin v. Löwis wrote:
> >>
> >> You may wonder what changed between before and now: we (the PSF) now
> >> have a good management of the forms, thanks to them being lis
On Wed, 16 May 2012 10:59:57 +1000, Nick Coghlan wrote:
> On Mon, May 14, 2012 at 9:23 PM, Nick Coghlan wrote:
> > I'm proposing we grant commit privileges to Daniel Urban.
> >
> > He's provided patches for a number of fixes and feature requests for
> > 3.2 and 3.3, including a particularly thorn
On Fri, 29 Jun 2012 02:23:12 +0200, Jesus Cea wrote:
> Python 3.3 is currently in beta, so the rythm of new patches in
> "default" will decrease and people with new features MUST wait until
> 3.3 is out. I think this is a waste of time. And even if people is
> working with HG private clones, they
Pat, I'm not sure what the technical difficulty was...I was just able
to update Flávio's entry. (If I did something wrong I'm sure you'll
fix it...)
--David
On Mon, 23 Jul 2012 09:43:22 -0400, Pat Campbell wrote:
> Hi Flávio:
>
> Thank-you for submitting your contributor agreement form to th
On Tue, 24 Jul 2012 23:18:51 +1000, Nick Coghlan wrote:
> On Tue, Jul 17, 2012 at 5:59 AM, Georg Brandl wrote:
> > On 16.07.2012 15:43, Antoine Pitrou wrote:
> >> Le lundi 16 juillet 2012 à 23:26 +1000, Nick Coghlan a écrit :
> >>> I just noticed that PEP 424 hasn't appeared on the site yet - i
On Sat, 18 Aug 2012 17:01:10 +0200, Christian Heimes wrote:
> Am 18.08.2012 15:08, schrieb Stefan Krah:
> > Christian Heimes wrote:
> >> Yup, my login still works. I can send you a CSV or XML report if you like.
> >
> > Thanks, got the CSV!
> >
> > If anyone has the possibility to create new ac
On Thu, 23 Aug 2012 01:32:21 +0200, Antoine Pitrou wrote:
> I'd like to propose Serhiy Storchaka as a new core developer. He has
> made numerous contributions, and has proven receptive to comments and
> reviews. He's also interested in becoming a core developer.
>
> What do you think?
+1 from me
On Fri, 24 Aug 2012 09:59:37 +1000, Nick Coghlan wrote:
> I'd like to propose granting Eric Snow commit privileges.
+1
--David
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
On Sun, Sep 23, 2012 at 6:20 PM, Ezio Melotti wrote:
> I would like to propose Chris Jerdonek as a new core developer.
+1
--David
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
On Mon, 01 Oct 2012 10:57:45 -0400, Terry Reedy wrote:
> On 10/1/2012 1:02 AM, Georg Brandl wrote:
>
> > You are right that we should have information about bugfix/security mode
> > and
> > about end-of-life; I propose to put them in the respective release schedule
> > PEPs.
>
> From the commit
On Tue, 02 Oct 2012 01:41:25 +0200, Jesus Cea wrote:
> On 01/10/12 14:23, Georg Brandl wrote:
> > I've now added lifespan information to the 3.2 and 3.3 release
> > schedule PEPs, perhaps Barry and Benjamin could do the same for
> > 2.6 to 3.1.
>
> http://python.org/dev/peps/pep-0398/
>
> """
>
On Tue, 16 Oct 2012 14:05:34 -0400, Barry Warsaw wrote:
> On Oct 16, 2012, at 10:11 AM, Gregory P. Smith wrote:
>
> >That isn't up to date and users cannot edit their own information (at least
> >it tells _me_ I'm not authorized when I submit the edit form on my own
> >info) so I wouldn't trust t
On Wed, 07 Nov 2012 14:26:15 +0100, wrote:
> What can we do? Apart from the obligatory joke of nudging him gently
> towards Ruby, I think calling his behavior out is a good idea. Cory
> Doctorow also thinks that "many trolls are perfectly nice in real life
> -- sometimes, just calling them on the
On Wed, 26 Dec 2012 02:36:08 -0500, Terry Reedy wrote:
> This is a continuation of my answer to Christian
>
> On 12/25/2012 5:56 PM, Åukasz Langa wrote:
> > 1. Communicate what happened clearly and openly to our community.
>
> I am not sure how broadly you mean 'our community', but please no.
On Wed, 26 Dec 2012 17:36:46 +0200, Andrew Svetlov
wrote:
> On Wed, Dec 26, 2012 at 3:30 PM, Nick Coghlan wrote:
> > Run through the sections here:
> > http://docs.python.org/devguide/coredev.html#gaining-commit-privileges
> >
> > The main one is for Serhiy to send an email with his public SSH k
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
> > conferences this year with people _afraid_ to get involved with core
> > development on the base of havi
On Wed, 26 Dec 2012 17:54:01 +0100, Antoine Pitrou wrote:
> Le mercredi 26 décembre 2012 à 08:08 -0800, Eli Bendersky a écrit :
> > At the risk of stating something that I imagine everyone already
> > knows, this list is itself publicly viewable:
> >
> > http://mail.pyt
On Wed, 26 Dec 2012 18:56:54 +0200, Ezio Melotti wrote:
> On Wed, Dec 26, 2012 at 4:18 PM, Brian Curtin wrote:
>
> > You're wasting your time if you think you will be the one to break
> > through to him after several people have already talked to him.
> > Apparently he even got on Skype with Gui
On Mon, 28 Jan 2013 12:53:10 -0500, "Kurt B. Kaiser" wrote:
> We received a contributor agreement by postal mail
>
> David Lam
> 211 E. Meadow Dr
> Palo Alto CA 94306
>
> [email protected]
>
> I've added it to the local paper files
I've updated his tracker entry to reflect receiving the form as of
On Mon, 28 Jan 2013 13:08:12 -0500, Jesse Noller wrote:
> On Monday, January 28, 2013 at 12:43 PM, Serhiy Storchaka wrote:
>
> > Several contributor agreement were send last months and wait for accepting.
> >
> > Ben Morgan (Ben.Morgan) http://bugs.python.org/issue12004
> Received by the PSF Adm
I'll be there the whole time (summit through the end of the sprints).
--David
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
On Tue, 26 Feb 2013 12:43:04 -0500, Brett Cannon wrote:
> On Tue, Feb 26, 2013 at 12:16 PM, Guido van Rossum wrote:
> > So we have nobody to lead the core sprint?
>
> ATM no.
>
> > Maybe we should change the
> > subject to "WANTED: core dev sprint leader for PyCon" ?
>
> Done.
>
> > Is this t
I applaud the foundation for getting an electronic signature method in
place.
However, I have to say that to my mind echosign is nothing more than
"authentication theater", and I wonder if it is going to make us look
more than a bit clueless to the tech community. I'm surprised that
a lawyer woul
On Mon, 04 Mar 2013 10:29:23 -0500, Jesse Noller wrote:
> On Monday, March 4, 2013 at 10:24 AM, R. David Murray wrote:
>
> > I applaud the foundation for getting an electronic signature method in
> > place.
> >
> > However, I have to say that to my mind
My apologies for sounding a sour note, by the way, I think I was unduly
influenced by my previous (very poor, from a UI perspective) experience
with a system like this, and had a knee-jerk reaction.
I think it is great that this system has been put in place, and my
thanks to all involved.
--David
On Mon, 04 Mar 2013 10:58:57 -0500, Jesse Noller wrote:
> On Monday, March 4, 2013 at 10:55 AM, Antoine Pitrou wrote:
>
> > > My apologies for sounding a sour note, by the way, I think I was unduly
> > > influenced by my previous (very poor, from a UI perspective) experience
> > > with a system l
On Sat, 16 Mar 2013 15:25:56 +0100, Georg Brandl wrote:
> Am 16.03.2013 15:01, schrieb Nick Coghlan:
> > Could someone with sufficient privileges please flip Peter Moody's
> > commit bit in the tracker: http://bugs.python.org/user9293
>
> Done.
>
> > Reminder to everyone else: if you have commit
+1
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
On Mon, 18 Mar 2013 15:17:23 -0700, Noah Kantrowitz wrote:
> As part of the PyCon sprints I would like to move python.org off
> dinsdale to a VM at OSL. Due to the build system being tied to SVN,
> I'll also migrate that service on the same VM. Do any SVN repos other
> than www/ need to remain ava
On Wed, 20 Mar 2013 12:47:09 -0700, Noah Kantrowitz wrote:
> +1 on let them break, but when they get fixed it should be against a
> dedicated testing endpoint if possible, preferably something internal
> to the test suite. Maybe spawn an HTTP server in a background
> thread/proc? I would very much
Note that I believe ECDSA is now the default for host keys for OpenSSH.
At the least, my systems (Gentoo) switched to them after an upgrade a
a bit a go.
--David
On Mon, 25 Mar 2013 13:29:48 +0100, Christian Heimes
wrote:
> Am 25.03.2013 05:51, schrieb Jeffrey Yasskin:
> > You missed that ECDSA
On Sat, 30 Mar 2013 13:41:39 +0100, Jesus Cea wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 28/03/13 08:55, Georg Brandl wrote:
> > with 3.2.4 being the last regular 3.2 maintenance release and the
> > rc out of the door, the 3.2 branch should only be committed to for
> > securi
On Sat, 30 Mar 2013 10:13:13 -0700, Ned Deily wrote:
> In article <[email protected]>,
> "R. David Murray" wrote:
> > This is the first time we've been in the situation of having a
> > security-only branch in Mercurial (other tha
On Fri, 24 May 2013 18:39:16 +0200, "Antoine Pitrou"
wrote:
> Brett wrote:
> >> Of course, we've talked about doing something like this before, it's
> >> just never irritated anyone enough for them to sit down and *write*
> >> the associated NEWS file generator, or the code to split the existing
On Fri, 24 May 2013 15:26:29 -0400, Brett Cannon wrote:
> On Fri, May 24, 2013 at 2:27 PM, Antoine Pitrou wrote:
> > Le vendredi 24 mai 2013 à 14:23 -0400, Brett Cannon a écrit :
> >> > You'll have to copy stuff by hand, though, if you don't want to rely on
> >> > the
> >> > merge machinery. S
1 - 100 of 180 matches
Mail list logo
