[python-committers] Python workflow quirks with mercurial and hg-git extension

I plan to come back to python development (about time!) but I truly hates git. I am experimenting with mercurial + hg-git extension and it is quite usable (after the initial painfully slow clone time), but I am having small quirks that I would like to iron out with a fellow more experienced or also

Re: [python-committers] Requirements to get the "bug triage" permission?

On 06/12/17 23:17, Victor Stinner wrote: > My problem is that we don't have a long list of "awards" in Python: > the triage bit and the commit bit... > > I had some ideas to create badges, but before I come with something > concrete, I'm trying to build something with what we already have ;-) I h

[python-committers] broken arm

;slow" but available, anyway. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [EMAIL PROTECTED] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:[EMAIL

Re: [python-committers] broken arm

still here :-). PS: If I was working in the bsddb code for Python 3.0 I would have spend Saturday working on this, instead of having fun in a birthday party with an aching end :-). Shit happens :) - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [EMAIL PROTECTED] - http://

Re: [python-committers] Cutting Python 2.6

I'm missing something... - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [EMAIL PROTECTED] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jab

Re: [python-committers] Cutting Python 2.6

ion you want... In fact, my approach would be to create a 2.6 branch after 2.6b3, and leave the trunk for 2.7 work. No, I am not voluntering as release manager O:-). If freezing the tree 24 hours is needed, that's fine. - -- Jesus Cea Avion _/_/ _/_/_/

Re: [python-committers] Luke Kenneth

l to check who was that "Luke Kenneth" :-). - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/_/_

Re: [python-committers] Survey about DVCSs compared to svn

ex.cgi/ForestExtension And a proposal for the core Mercurial: http://www.selenic.com/mercurial/wiki/index.cgi/NestedRepositories - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabb

[python-committers] help with svnmerge

ow to merge using pure SVN and Mercurial... O:-) - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/_/

[python-committers] What is the state of mercurial migration?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, everybody. I have read PEP 385, but there is no time schedule there, and I was wondering how is the migration done. Any idea of when can we use Mercurial to do our contributions?. - -- Jesus Cea Avion

[python-committers] Why r69846 is not merged to "release26-maint"?

anything?. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:[email protected]

Re: [python-committers] Why r69846 is not merged to "release26-maint"?

l try to merge that patch, although it is old and will probably generate a ton of conflicts. Let's see... - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/

Re: [python-committers] Why r69846 is not merged to "release26-maint"?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Benjamin Peterson wrote: > 2009/7/2 Jeroen Ruigrok van der Werven : >> -On [20090702 17:15], Jesus Cea ([email protected]) wrote: >>> Ughhh. This is actually a good reason to migrate to mercurial, were >>> merges are pain

Re: [python-committers] Why r69846 is not merged to "release26-maint"?

chnology helps. The merge features of SVN 1.5 are limited but blessing. But I don't want to start a flamewar. The issue is already settled. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _

Re: [python-committers] Why r69846 is not merged to "release26-maint"?

't > introduce any new syntax or tweak semantics. If that is true (I agree with that policy, btw), please confirm "officially". Can we forget about 3.0 branch?. Can I delete that checkout from my system?. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j

Re: [python-committers] Why r69846 is not merged to "release26-maint"?

days ago, with *no* (zero) answers. How is it going?. Can I help in any way?. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/

[python-committers] Berkeley DB (Was: Re: r73807 - python/branches/py3k/setup.py)

tion...). But I don't want to open-fire just now... O:-). - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber /

Re: [python-committers] Berkeley DB (Was: Re: r73807 - python/branches/py3k/setup.py)

you could take > a look at that? I am not aware of that. I only check buildbots after doing commits. If somebody has a buildbot reference, please share. I promise to work to solve it. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected]

Re: [python-committers] Data corruption issue (C IO library)

ecially in Python 3; otherwise, people will think we still don't > consider it ready for use. +1. Messing with people files is probably the worst you can do. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/

Re: [python-committers] branches and merging

anything else holding us back?. (And yes, maybe migrating would do people angry enough for solving the last details :-). - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@ja

Re: [python-committers] branches and merging

ic, assuming that I don't > have to spend much of my time on the EOL issues. Do you have a list of -detailed- pending issues?. Detailed enough to decide if we can help or not... - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jce

Re: [python-committers] SSH keys and Keychain

y to uninstall it > first. Then verify in Applications ? Accessories ? Passwords and > Encryption Keys that Seahorse sees your SSH key. I would use "ssh-agent" directly, via "ssh-add". It is what I do. - -- Jesus Cea Avion

Re: [python-committers] SSH keys and Keychain

Do the test against a machine you can update new SSH keys to. PS: Just for trying, check if your SSH key has \013 inside (Carriage Return). If it does, *DO A COPY* and delete those special chars, just for testing. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/

Re: [python-committers] branches and merging

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/02/2010 02:21 PM, A.M. Kuchling wrote: > On Tue, Mar 02, 2010 at 04:36:42AM +0100, Jesus Cea wrote: >> I can't wait for HG. I have read the main cutprit for the delay is the >> line-ending issue with MS Windows developers. Is

Re: [python-committers] branches and merging

se, clone a single branch, like this: > http://hg.python.org/cpython#py3k, and that should prevent you from > getting the error even on subsequent pulls. I tried this, but I get the error again, unless I do a "pull" for that branch only. A "pull" with no options gi

Re: [python-committers] branches and merging

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/10/2010 04:30 PM, Jesus Cea wrote: > On 03/10/2010 08:29 AM, Dirkjan Ochtman wrote: >> So, in the meantime, if you have ssh access, make your clone via ssh. > > Could you possibly the exact command to use to clone cpython HG &

Re: [python-committers] branches and merging

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/13/2010 04:01 AM, Antoine Pitrou wrote: > Le Sat, 13 Mar 2010 00:11:51 +0100, > Jesus Cea a écrit : >> >> I still don't know how I can clone the cpython repository. Regular >> clone doesn't work with current r

Re: [python-committers] Fw: [Python-checkins] r78823 - python/tags/r265rc2

y necessary. 2.6.5 final is scheduled for 2010-03-19. I was wondering about http://bugs.python.org/issue3928 . It is a trivial fix a couple of lines long only. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/_/

[python-committers] Is 3.1 open? (was: Re: Fw: [Python-checkins] r78823 - python/tags/r265rc2)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/13/2010 11:25 PM, Barry Warsaw wrote: > On Mar 13, 2010, at 08:42 PM, Jesus Cea wrote: > >> I was wondering about http://bugs.python.org/issue3928 . It is a trivial >> fix a couple of lines long only. > > These ca

Re: [python-committers] Is 3.1 open?

3.1 branch after 2.6.5 and 3.1.2 are out. Should I commit now to trunk/py3k and later to 2.6/3.1, or wait to do the four commits at the same time?. Don't want to miss the 2.7beta. Mercurial, where are you?. This would be a non issue :) - -- Jesus

Re: [python-committers] Is 3.1 open?

y or using a tool like http://mercurial.selenic.com/wiki/TransplantExtension . The devil is in the details, like how the release manager repository clone accesses buildbots, for instance. This is possible workflow. I don't know what is the actual plan, yet. - --

Re: [python-committers] svnmerge init on py3k branch fails..

> Possible change: "This 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)." I "perpetrated" the same error a couple of years ago. Fortunatelly I saw the issue before committ

[python-committers] pybsddb 5.0.0 integration and 2.7beta1 schedule

d a couple of hours for integration, but beware timezone! (Spain :). - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j.

Re: [python-committers] pybsddb 5.0.0 integration and 2.7beta1 schedule

this sounds a bit optimistic. pybsddb 5.0.0 compiles against BDB 5.0.x, but it doesn' support any new feature. The diff is pretty small, and the testsuite is very extensive. I am pretty confident. - -- Jesus Cea Avion _/_/

Re: [python-committers] pybsddb 5.0.0 integration and 2.7beta1 schedule

in 2.7.1 we want to support Berkeley DB 5.0.x (already released a week ago), we must break API anyway, because some constants have been renamed, and some defaults have been inverted. - -- Jesus Cea Avion _/_/ _/_/_/_/_

Re: [python-committers] Blocking commits to 2.6

. :) Mercurial can not come soon enough :). - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber

Re: [python-committers] When do we stop automerging from trunk to py3k?

tomatic that cherrypicking patches, with the risk of forgeting some. I can't wait for HG native use, and I am curious about the exact workflow we are going to use. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jc

Re: [python-committers] When do we stop automerging from trunk to py3k?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28/04/10 12:17, Antoine Pitrou wrote: > Le mercredi 28 avril 2010 à 04:37 +0200, Jesus Cea a écrit : >> That is, patch 2.7 and "push" those changes to 3.x, undoing the >> unnecesary patches with a simple "backou

Re: [python-committers] branches and merging

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/03/10 03:13, Jesus Cea wrote: > On 03/02/2010 02:21 PM, A.M. Kuchling wrote: >> On Tue, Mar 02, 2010 at 04:36:42AM +0100, Jesus Cea wrote: >>> I can't wait for HG. I have read the main cutprit for the delay is the >&g

Re: [python-committers] branches and merging

won't change. I know. It is what I do daily. I can not pass without Mercurial Queues :). I dream every night with the day I can use Mercurial natively :-pp. I was just confirming that the "issue" I had with mercurial two months ago (trying to clone a repository with a lot

Re: [python-committers] 2.7 almost out the door

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/07/10 17:45, Benjamin Peterson wrote: > 2.7 has been tagged, and I have uploaded docs and the source tarballs > to python.org. I will wait on binaries before announcing the release. The end of an era. Congratulations to all. - -- Jes

Re: [python-committers] PEP checkin process

e to work by > overriding PYTHON as Benjamin suggests). Not only that, but the > makefile builds all the PEPs when I generally only care about the PEP > I'm working on and PEP 0. The "make" should include dependency information to only

[python-committers] Mercurial Status?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 How is migration to Mercurial going?. Showstoppers?. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:[email protected]

Re: [python-committers] Mercurial Status?

aking the > repositories the main development ones. Ok. Thanks for providing a schedule :). Good luck (and justice!) with your (both) thesis. Uhmmm, what is the plural for thesis, in english?. In Spanish it is the same word, changing the prefix article: "la tesis"/"las tesis&

Re: [python-committers] trunk is open

remains intact. All these will be meaningless after we finish the mercurial migration. God, it is about time :-). - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/

Re: [python-committers] New hg repo ssh URIs

onsidered preferable. Are those repositories read/write?. What is their use TODAY?. Only for being ready for 12 december?. The push will be thru SSH only?. No option for HTTPS pushing?. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://ww

Re: [python-committers] Blocking feature backports

g our own > patches, but otherwise I think that it isn't being used. Remember that after 12th December, with Mercurial becoming the primary version system, the dynamic will change a lot. Still 12 days to go. I will be very happy :). - -- Jesus Cea Avion _/_/ _/_/_

Re: [python-committers] Blocking feature backports

ars since Mercurial decision was done, let me daydream a bit :-). And I do actually have confidence that the people on charge of this migration have set a realistic milestone. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] -

Re: [python-committers] Providing .tgz sources

know about xz yet (not to mention old Debian / RHEL > machines). So I would vote to continue providing .tar.bz2 and/or .tgz > tarballs. Providing XZ files *IN ADDITION* to gz/bz2 will increase the mindshare for the format. I am checking the webpage and installing the XZ tools just now :-

Re: [python-committers] Blocking feature backports

deferral of beta1 until mercurial migration. Anything pushing mercurial migration would be good. But Beta1 is already out... Would be shameful to manage 3.2.x using svn... - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea

Re: [python-committers] Partial commit privileges

ifference between core committers and external developers will diffuse. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _

Re: [python-committers] New contributors, don't forget to send in a contributor form!

; form: http://www.python.org/psf/contrib/ ASAP. Maybe would be a good idea to write down a checklist for new committers: get a mentor, send the SSH key, be sure have signed the contributor agreement, subscribe to the right mailing lists... - -- Jes

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

ycon 2011 will mark the second anniversary of Guido's pronouncement. If we > do nothing else in Atlanta, can we *please* *please* *please* come away from > there with the conversion operationally completed? +inf!. - -- Jesus Cea Avion _/_/ _/_/_/

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

"backports" from the main development line (that is, backport to candidate release from the mainline), those "doesn't count" to the complexity. Ideally, a release candidate clone would have very few patches, and most of them coming from the main development (or main bra

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

try to merge back (same patch present in both lines, but no metadata saying so). But that seems an issue with current HG/cherrypick extension, not with an abstract mercurial inability. In fact, python could be a push to improve that in HG. - -- Jesus Cea Avion

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

t there only things that MUST be in 3.3.0. For general development, commit to "py3k"". Anybody can merge from "beta" *TO* "py3k", for "up porting". The trick here is to patch the oldest supported version, and "up

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

that a patch is already manually committed in both lines, and cope with that gracefully when merging. I am sure we are not alone with these issues, and I hope somebody is actually doing something about it. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected]

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/02/11 13:04, Nick Coghlan wrote: > On Thu, Feb 3, 2011 at 10:37 AM, Jesus Cea wrote: >> In fact, "up-porting" is usually better, because you don't have to think >> if you must downport or not. Versión "n+1&quo

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

it is done "automagically" vía mercurial merges. That is the point... - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/02/11 10:54, Nick Coghlan wrote: > On Fri, Feb 4, 2011 at 1:17 PM, Jesus Cea wrote: >> "Up-porting" CAN'T be forgotten because it is done "automagically" vía >> mercurial merges. That is the point... &g

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

s, doing thing "the right way" would help too. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_

Re: [python-committers] Create a Mercurial repository with a branch per issue

Rebasing is good before committing to the "real" repository, but anybody with a checkout clone will suffer. I guess the clone should be automatically destroyed as soon as the clone is merged back to the real repository. - -- Jesus Cea Avion

Re: [python-committers] Create a Mercurial repository with a branch per issue

on has a patch in his own repository, and you try to merge back, you will get again the original changeset list, two heads, etc. As a general rule, rebase should be done ONLY in personal clones not shared by anybody. Or, in this particular case, a clone

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

candidate. Patching is very restricted. If we had a 3.2.0 release candidate clone, MUST SHIP changes would be in the 3.2.0rc repository, but patches planned for 3.2.1 would be being already being committed the clone. When 3.2.0 is released and the branch is marked as "maintenance", the 3.2.

Re: [python-committers] Create a Mercurial repository with a branch per issue

ributors is > going to grow with Python under a DVCS +1. But first we need the mercurial switchover to be done and to get some first hand experience before writing down the best practices *wiki* :). - -- Jesus Cea Avion _/_/ _/_/_/

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

;F->G->H When you merge you have: A->B->C->D->I \ / \->E->F->G->H-/ Code in "I" contains all "B", "C", "D", "E", "F", "G" and "H". This merging is "a

Re: [python-committers] Create a Mercurial repository with a branch per issue

es [...] - -M --no-merges do not show merges [...] """ Would be interesting that "bisect" would be "improved" to follow only the first parent in a merge. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - h

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

Not sure if this should be a real rule, but if "old" and "new" reside in the same repository (for instance, named branches), you can check this in the push "hook" living in the server. That is, the hook check that the changesets you are pushing don't create a new

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

e in trunk). Solving this conflict is trivial (just drop that change), and now you can retry merging again, this time successfully. Ideally, when you push to the repository, you push your patches *AND* the merges, all in an atomic operation. So you don't move the merge burden to somebod

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

is still hanging around. Or you can force this via a push "hook": no heads left behind! :-) I just wrote an email about this. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ ja

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

3.x fixes to 2.7, of even worse, developing your patches in 2.7 and "up-porting to 3.x"... That is an entirely different topic. With current python-dev commitment, any bug discovered in 3.1 that affect 2.7, should be solved in both. In fact, 2.7 fixing should more priori

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

want the option to include arbitrary repositories around in the buildbot infraestructure for, let say, developing long term features. 2.7: maintenance branch. 2.7.x: clone of 2.7 to host patches for 2.7.x when 2.7 is closed (RC state) getting ready for releasing 2.7.(x-1). - -- Jesus Ce

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/02/11 01:07, Antoine Pitrou wrote: > > Le samedi 05 février 2011 à 01:00 +0100, Jesus Cea a écrit : >>> Someone could sit and produce a >>> written proposal evaluating the various possibilities, and we can >>&

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

d it over. Could I read it too?. I have been using HG for the last three years, at least. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@j

Re: [python-committers] [PSF-Members] [Fwd: Re: Push rights for Ross Lagerwall]

and investing time being sure everything is ok. That said, I have used the same PGP key for 15 years. Would be nice if a digital signature would be enough. I am probably an exception, nevertheless. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] -

Re: [python-committers] PEPs repo converted

documented somewhere... :). BTW, can I actually push to "hg.python.org/peps", as indicated?. I would expect something like "ssh://[email protected]/peps". - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea

Re: [python-committers] PEPs repo converted

ne other than python.org. > Those who edit the PEPs just need to keep the $Revision$ and $Date$ > intact. So, must I disable the extension KW again?. I am confused. Maybe editors simply must keep "$Revision$" and "$Date$", since those keywords are expanded in the

Re: [python-committers] PEPs repo converted

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 PEP 0001 still lists SVN as the way to checkout/commit PEPs. I guess that place would be the right place to document the details about keywords & mercurial. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jce

Re: [python-committers] Committer rights for Nadeem Vawda

[email protected]? > Or? What is preventing me to send a fake SSH key to that acount, from a gmail address, saying "hi, this is Nadeem. You are waiting for this" ;-). - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@

Re: [python-committers] Committer rights for Nadeem Vawda

ly pointless considering you already have > commit privs... When I -slowly and sneaky- trojanize socket module and, additionally, add all the buildbots to my spambot network, I will not use my own SSH key. I promise :). I should quit IT security and grow vegetables somewher

Re: [python-committers] Committer rights for Nadeem Vawda

ere can I find your PhD online? :). (Congrats for your recent PhD!) - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/

Re: [python-committers] Committer rights for Nadeem Vawda

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/04/11 04:48, Jesus Cea wrote: > Too late. Being in the field for the last ~15 years cualifies me as > "please, don't ask me what I do for a living in your party, if you > expect to sleep comfy tonight". Do not ask me e

Re: [python-committers] English 'precise' is only an adjective, not a verb.

Don't ask me for the plural of "virus" in different lenguajes :-p. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/

Re: [python-committers] 3.2.1 rc 2

one week later. Would you comment about the push policy to 3.2 branch?. Are you doing the release work in a separate clone?. Can we push to 3.2 with no restrictions?. That would be a very nice side effect of mercurial migration. - -- Jesus Cea Avion _/_/ _/_/_/

Re: [python-committers] Mercurial upgrade

is... quite experimental and not garanteed:). And yes, I have read your posts to HG development mailinglist in May, and I have big hopes for "generaldelta" or something close to it. But I will wait until is "official" (luckily activate per default for new repositories/network c

Re: [python-committers] Mercurial upgrade

on. I am fine with that, if somebody with access takes care to do a "hg verify" frequently :). - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://w

[python-committers] Cutting 3.3 branch now. Why not?

!). No need to "press me" with an ¿obsolete? technical limitation. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:[email protected] _/_/_/_/ _/_/_/_/_/ .

Re: [python-committers] Cutting 3.3 branch now. Why not?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29/06/12 10:07, Georg Brandl wrote: > And as Ross says: you *can* use the buildbots for personal > branches. I missed that. How is it done?. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected]

[python-committers] Alexander Belopolsky

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexander Belopolsky is a core developer but the bugtracker doesn't have a "contributor form received" flag for him? An oversight?. Can anybody check the forms and change the flag? Check: Thanks!. - --

Re: [python-committers] Alexander Belopolsky

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/09/12 03:09, Alexander Belopolsky wrote: > FWIW, here is what Martin wrote to me ~ 1.5 years ago. If the > form has not been found by now, it probably cannot be found at all. > I have no problem resubmitting it again if necessary. I had to send

Re: [python-committers] Alexander Belopolsky

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 25/09/12 13:26, Georg Brandl wrote: > May I note that it's commonly considered bad practice to put the > name of a person in the subject without any explication? E.g. > "Commit privileges for Chris Jerdonek" is fine, "Alexander > Belopolsky" is not

[python-committers] Branches support status (Re: 3.3 branch created in main repository)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29/09/12 10:35, Georg Brandl wrote: > Until the last ordinary 3.2 bugfix release is done (which will be > soon), the usual procedure for 3.x will be to check into 3.2, merge > into 3.3, and then merge into default, except of course for a) > fixes of

Re: [python-committers] Branches support status (Re: 3.3 branch created in main repository)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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/ """ 3.3 Lifespan 3.3 will r

Re: [python-committers] Branches support status (Re: 3.3 branch created in main repository)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/10/12 02:25, R. David Murray wrote: >> 3.3 will receive bugfix updates approximately every 4-6 months >> until one release after the release of 3.4.0 final. After that, >> security [...] > As a native English speaker it is not immediately obviou

Re: [python-committers] Anatoly Techtonik's contribution

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26/12/12 17:38, Brian Curtin wrote: > On Wed, Dec 26, 2012 at 10:20 AM, Ezio Melotti > wrote: >> And a side effect of being welcoming is that you get every kind >> of people. Different people have different behaviors and skills. >> I don't think hi

Re: [python-committers] MSDN subscriptions - new or renew

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I was wondering if we could ask Oracle (pufff) about Solaris 10/11 patch support :-?. - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j.

Re: [python-committers] Please don't commit to 3.2 branch anymore

-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 > security releases. So please don't commit anything there anymore. > To he

Re: [python-committers] Please don't commit to 3.2 branch anymore

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30/03/13 15:15, R. David Murray wrote: > This is the first time we've been in the situation of having a > security-only branch in Mercurial (other than 2.7, which is its own > head). So I don't believe we have articulated a procedure yet. I am ask

Re: [python-committers] Please don't commit to 3.2 branch anymore

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30/03/13 16:10, Jesus Cea wrote: > Something simple would be for the hook to refuse any commit in > that branch UNLESS it is coming from the maintainer. BTW, are the hooks available anywhere. I am interested in the "create patch"

Re: [python-committers] Relicensing source code for inclusion in Python

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/04/13 18:30, Antoine Pitrou wrote: > I wrote to the authors (Brendan Cully and Mads Kiilerich) and got > their informal approval for relicensing and inclusion in Python. They could sign the contributor agreement and then propose a patch for incl

  1   2   >