[python-committers] Re: getting old branches/releases

>> I'm trying to get the 3.3 and 3.4 branches so I can check my libraries >> compatibility with older versions, but I do not see those branches as being >> available: >> >> How can I get those? >> >> > > > 3.3 and 3.4 existed before the migration from GitHub, so we don't have the > branches. >

Re: [python-committers] [Core-mentorship] Regarding reviewing test cases written for tabnanny module

On 12 April 2017 at 03:10, Mariatta Wijaya <mariatta.wij...@gmail.com> wrote: > Back to the original issue with reviewing the PR > https://github.com/python/cpython/pull/851 > > Other than not being able to review the diff, is there any other problem? > Can the PR be revie

Re: [python-committers] [Core-mentorship] Regarding reviewing test cases written for tabnanny module

his discussion to >> the python-committers list rather than core-mentorship. >> >> On Mon, Apr 10, 2017 at 12:12 PM, Terry Reedy <tjre...@udel.edu> wrote: >>> >>> On 4/10/2017 12:54 PM, Guido van Rossum wrote: >>>> >>>> So th

Re: [python-committers] 4 weeks with the new workflow: what needs changing?

> On Mar 10, 2017, at 5:13 PM, Brett Cannon wrote: > Is the mention bot helpful? (Our config is at > https://github.com/python/cpython/blob/master/.mention-bot and the docs are > at https://github.com/facebook/mention-bot) On 11 March 2017 at 00:32, Donald Stufft

Re: [python-committers] autoconf 2.70

>> On 11/22/2016 08:16 PM, Ned Deily wrote: >> > On Nov 22, 2016, at 11:06, Xavier de Gaye wrote: >> >> The configure file on the default and 3.6 branches have been generated >> >> with autoconf 2.70 once again. This is annoying when you have to >> >> maintain patches to

Re: [python-committers] Here's what's going into 3.5.2 final and 3.4.5 final

On 24 June 2016 at 09:29, Matthias Klose wrote: > On 24.06.2016 11:14, Larry Hastings wrote: >> Heads up! This is a courtesy reminder from your friendly 3.4 and 3.5 release >> manager. Here's a list of all the changes since 3.5.2rc1 that are currently >> going into 3.5.2 final:

Re: [python-committers] Deprecation Policy PEP

> 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 it's better to be conservative, and if the API is >

Re: [python-committers] Deprecation Policy PEP

On 29 January 2016 at 21:59, Serhiy Storchaka wrote: > On 29.01.16 21:56, Ezio Melotti wrote: >> On Fri, Jan 29, 2016 at 8:00 PM, Serhiy Storchaka >> wrote: >>> Some deprecation can be documentation-only. >> >> Do you have examples where this has been

Re: [python-committers] [Python-checkins] cpython (merge 2.7 -> 2.7): merge heads.

On 3 September 2015 at 10:03, Senthil Kumaran wrote: > I did a merge head with Victor's change in 2.7 before pushing my change. > Can someone confirm if I did it right? If anything was wrong, how to correct > it? It looks like you did it right. If I compare the merge result

Re: [python-committers] [Python-Dev] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

, and a post-push hook on the repository to trigger the build. It's actually possible to configure a bitbucket POST hook to trigger a buildbot build, but we haven't yet integrated that into the buildbot master. Regards, Martin -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment

Re: [python-committers] [Python-Dev] Do we need to sign Windows files with GnuPG?

cycle. I had asked the PSF for a StartSSL certificate when the previous certificate expired, and the PSF was not able to provide one. After waiting several weeks for the PSF to provide the certificate, Kurt then kindly went to Verisign. Kind regards, Martin

Re: [python-committers] Time for a 3.4.3?

in early 2015. Regards, Martin ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] 3.4 buildbots??

, by targeting them to http://hg.python.org/buildbot/empty/ once, and triggering a rebuild. Regards, Martin ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] default hg.python.org/cpython is now 3.5

? Typically we do one last release before shutting the last bugfix branch down, but that's Georg's call since 3.3.5 was released so recently. Given that, I propose 3.3 goes into security fix mode immediately. +1 Martin ___ python-committers mailing list

Re: [python-committers] 3.4 buildbots??

Am 17.03.14 16:58, schrieb Jesus Cea: On 17/03/14 15:16, Martin v. Löwis wrote: However, I would advise against doing so now, and delay the addition of the 3.4 branch until 3.3 is retired from bug fixing, and then repurpose all 3.3 configuration for 3.4. Otherwise, some slaves might run out

Re: [python-committers] Code review tool (rietveld) bug

Am 27.01.14 21:24, schrieb Antoine Pitrou: As a sidenote, why is Larry green on this page? Because he used the keyword LGTM. Regards, Martin ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo

Re: [python-committers] Code review tool (rietveld) bug

/a which really ought to fill out the in_reply_to field (with Message_2687) If anybody wants to investigate: the source of this is at http://hg.python.org/tracker/rietveld Regards, Martin ___ python-committers mailing list python-committers@python.org

Re: [python-committers] Code review tool (rietveld) bug

). Regards, Martin ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Updated schedule for Python 3.4

of sitting idle, they actually start working on bugs, and contributing to finishing the release. With a DVCS, there is of course an alternative, where one could start working on new features while the trunk is in feature-freeze. Regards, Martin ___ python

Re: [python-committers] Anatoly has been warned about his behaviour potentially leading to his loss of tracker privileges

necessarily follow that banning someone is a better response. I think it is. Based on past experience, it would be temporarily anyway, and it may buy us a year or so of mental peace. Regards, Martin ___ python-committers mailing list python-committers

Re: [python-committers] Anatoly has been warned about his behaviour potentially leading to his loss of tracker privileges

role (meaning that it makes no difference whether you are logged in or not). Regards, Martin ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Closing the 2.6 branch?

*think* we have a hook on the master that prevents further pushes to the branch. Also, can anybody think of anything in the devguide that needs to be updated? Not the devguide. If anywhere, in PEP 101. Regards, Martin ___ python-committers mailing list

Re: [python-committers] Reminder: Python 3.4 alpha 1 release is Saturday August 3

, and 24h is not at all unrealistic. That, or some text explaining what to expect, would be good to have. It's easy enough: the tag is likely to occur 24h before the scheduled release. Regards, Martin ___ python-committers mailing list python-committers

Re: [python-committers] SSH fingerprint

://utcc.utoronto.ca/~cks/space/blog/tech/SshAndMitM Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] [Infrastructure] test suite dependencies on www.python.org

of incoming links to various pages. These need to be preserved as much as feasible (possibly using redirects). Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

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

for this kind of behavior: I still think he fits the description in http://www.youtube.com/watch?v=Q52kFL8zVoMfeature=gv I think he is poisenous to the Python project. If you haven't seen the video, please watch it all. Regards, Martin ___ python

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

and them somebody fixing them is something that could work. Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

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

decision (that I'm aware of) is that 2.7 should be supported indefinitely, which is not infinitely. Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] PEP repo access for Daniel Holth

control; he should just stick to committing where he is supposed to (just as everybody else). Key managers are currently Georg Brandl, Antoine Pitrou, and Brett Cannon. I keep forgetting whether there is an email alias for them. Regards, Martin

Re: [python-committers] anyone still have access to the coverity scan results?

in mind, they actually do demonstrate a real interest in free software. Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Further hg maintenance

On 02.07.2012 00:48, Martin v. Löwis wrote: I'll report if we found something that can be considered a permanent solution. Antoine managed to reduce the memory usage of Mercurial quite drastically. Not sure which contributed most, but a) hg was upgraded to 2.2 b) a patch was applied to hgweb

Re: [python-committers] [pydotorg-www] Deleting code.python.org

! Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

[python-committers] hg machine migrated

We (primarily Antoine) just migrated hg.python.org to OSU/OSL. Everything should continue to work as it did before, except that the IP address of the machine has now changed. If there are any issues, please let us know. Regards, Martin ___ python

[python-committers] Further hg maintenance

found something that can be considered a permanent solution. Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Contrib forms

have put EungJun Yi into Misc/ACKS (for doing the research), and asked him for a contributor form. If we are to require a signed agreement from smaller changes too, the devguide should be updated. Will do! Regards, Martin ___ python-committers mailing

Re: [python-committers] Commit privileges for Daniel Urban

at the moment would gain a desirable reduction of workload if Daniel could push changes himself). Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Allegro Group Contributor

as if these people had individually submitted a contributor form. Regards, Martin On 01.05.2012 17:32, Pat Campbell wrote: Hi Maria: Thank-you for submitting your CLA. Pat 2012/4/30 Maria Lysek maria.ly...@allegro.pl mailto:maria.ly...@allegro.pl Hello, __ __ I am pleased to send you CLA

[python-committers] Contrib forms

of the forms, thanks to them being listed in Roundup, and thanks to Pat (Campbell) keeping track of all forms that we receive. So we (the committers) are now in a position to actually verify that we have a contrib form received before deciding whether or not to commit a patch. Regards, Martin

Re: [python-committers] committer icon

I noticed that I don't have that fancy python logo next to my name on the bug tracker, indicating that I am a committer. Is that fixable? My user account is krisvale. Done! Martin ___ python-committers mailing list python-committers@python.org

Re: [python-committers] security and bugfix releases tagged

Am 24.02.2012 17:49, schrieb Benjamin Peterson: Hi Ned and Martin, 2.7.3rc1 and 3.2.3rc1 are tagged in the repo ready for binaries. 1b605fb13977c887a9554a9896b8 16081986 python-2.7.3rc1-pdb.zip 53439ec0110345225f5f0951f00bc387 17220674 python-2.7.3rc1.amd64-pdb.zip

Re: [python-committers] 2.7.2 and 3.1.4 rc now

until the final release, and any changes are only merged afterwards. This is a mess. Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Python 2.6.7rc2

than that. If the hg and svn changes are in the same order, and have the same commit messages (as they should), you can look at the log of the hg branch to find out what the youngest change is that has been copied; all changes that are more recent then still have to be applied. Regards, Martin

Re: [python-committers] Python 2.6.7rc2

(which is not a new requirement), so after synching, NEWS should be identical in svn and hg. Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Python 2.6.7rc2

you or me. It would be better, IMO, if there was a single developer who would migrate changes to svn, or to have some semi-automatic procedure for that. Regards, Martin ___ python-committers mailing list python-committers@python.org http

Re: [python-committers] Python 3.2.1 schedule amendment

Martin, Ned: I would say it's not mandatory for the beta release to have binaries, but you might want to test out your toolchains against the new process too. Indeed. I'd prefer if the release clone is public somewhere, so that I can point my local clones to it. Regards, Martin

Re: [python-committers] History lost in svn to hg conversion

to svn (i.e. multiple projects in one repository) is so uncommon that the Mercurial people are likely to ignore problems arising out of it. Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman

Re: [python-committers] History lost in svn to hg conversion

the full history). So it might have been possible to deal with it, had it been noticed. Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

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

the Englishmen failed to accept that import :-( The best the dictionaries come up with (besides to specify) is to state more precisely, to render more precisely. Regards, Martin ___ python-committers mailing list python-committers@python.org http

[python-committers] Recording committer status in the bug tracker

I added a boolean flag to the bug tracker indicating what user accounts belong to committers. Please check that the flag is set in Your Details, Is Committer. If it's not, please let me know. Regards, Martin ___ python-committers mailing list python

Re: [python-committers] SVN repository is now read-only

; the repository is read-only (IIUC) Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] http://www.python.org/3.2.(x|0) do not exist

Am 24.02.2011 02:39, schrieb Brett Cannon: Not sure if Martin is the only person who can fix this, but it would be nice to have those URLs working. I have added a redirect for 3.2.x. I haven't added one for 3.2.0, since we currently don't have any redirects for X.Y.0, only for X.Y. Regards

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

to your current setup, except that a) changes flow into the other direction, and b) there is no server communication to move patches across branches (whereas in subversion, you commit to the server, then svnmerge from the server). Regards, Martin

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

keeps track of what patches have been transplanted, but I doubt it. In any case, this discussion reiterates my point that this project (Mercurial migration) really needs a project lead, who then will also pronounce on usage policies. Otherwise, it's doomed to fail. Regards, Martin

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

into this to your taste. Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

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

(no report if no pending merges), either to python-dev or to the original committer (it might be also possible to determine the original pusher, and send mail to him instead). Regards, Martin ___ python-committers mailing list python-committers@python.org http

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

it is now with svnmerge (since you first have to transplant, and then merge back the transplanted patch, which should come out as a no-op - but the merge must be recorded). Regards, Martin ___ python-committers mailing list python-committers@python.org

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

compatibility, and another version that fixes it in the right way. I think I regularly contributes two or three such changes to every feature release of Python. I think a few other committers have also written such changes over time. Regards, Martin ___ python

Re: [python-committers] Commit rights for Ned Deily

and subscribe to the committers list, and give any instructions you deem necessary. Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Providing .tgz sources

: Python-2.7.tgz 32059 Python-2.7.tar.bz2 24986 python-2.7.msi577240 In November, the numbers were Python-2.7.tgz 24535 Python-2.7.tar.bz2 20797 python-2.7.msi 569328 Regards, Martin ___ python-committers mailing list python-committers

Re: [python-committers] Blocking feature backports

to Mercurial in the middle of release candidates. I expect the initial release using Mercurial to just not work, plus I plan to need several days to make the release. Doing so under the time pressure of a release candidate is not something I look forward to. Regards, Martin

Re: [python-committers] Providing .tgz sources

Am 05.12.2010 20:40, schrieb Jeroen Ruigrok van der Werven: -On [20101205 20:23], Martin v. Löwis (mar...@v.loewis.de) wrote: For those of us involved in the release process, every single file is a big problem, indeed. Seriously. Correct me if wrong, but isn't rolling up a tgz, tbz2, or txz

Re: [python-committers] Blocking feature backports

will happen next year. Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Deny nonbreaking spaces in the precommit script?

We don't gain anything by not implementing automation. I certainly gain something: spare time where I can work on other stuff than fulfilling infrastructure wishes of people. Regards, Martin ___ python-committers mailing list python-committers

[python-committers] Branch status (2.5 etc)

for bug fixes. Releases will be made by Benjamin regularly. Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Adding file temporary for debugging sake.

with the slave admin and ask him to clean the buildbot before anything can proceed. Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Adding file temporary for debugging sake.

a single buildbot, it might be best to create a branch, and then manually trigger a build of that branch on the build slaves that interest you. Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman

Re: [python-committers] Bump up tracker privs for asksol

Am 27.08.2010 15:28, schrieb Jesse Noller: Can someone with the power make sure Ask (asksol) has dev-level privs on the tracker? Benjamin took care of that. Regards, Martin ___ python-committers mailing list python-committers@python.org http

Re: [python-committers] Commit Privileges for Ask Solem

branches (dead: =2.4, 3.0, security-only: 2.5, 2.6, bug fixes only: 2.7, 3.1, new features: 3k) Unless somebody disagrees, please have him sent me his SSH key, and apply for python-committers. Regards, Martin ___ python-committers mailing list python

Re: [python-committers] Windows issues blocking alpha1

the external-common.bat for OpenSSL 1.0.0a. This is now fixed. There is a related problem - apparently, OpenSSL now fails to build on AMD64. I look into this later today. Regards, Martin ___ python-committers mailing list python-committers@python.org http

Re: [python-committers] Windows issues blocking alpha1

area, and it currently retries. Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Windows issues blocking alpha1

Am 31.07.2010 13:50, schrieb Antoine Pitrou: Le samedi 31 juillet 2010 à 11:23 +0200, Martin v. Löwis a écrit : Also, the Windows 3.x buildbot shows failures compiling _ssl and _hashopenssl (for logs, see e.g. http://bit.ly/aSAnhh). I'd like to know if this is specific to that machine (I've

Re: [python-committers] New comitter proposal: Terry Reedy

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 we should give them to him :) Has he actually contributed code to Python in all this time? Regards, Martin

Re: [python-committers] changes after 2.7 final

on everybody, it better be widely agreed (i.e. the people being forced to do things should, in principle, agree that these are good things). Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo

Re: [python-committers] Delaying 3.2 release

were not in place when we made the switch. Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Untabifying the C codebase

Antoine patched the 4 most important branches. Do we you have other active branches? Define active. The 2.5 maintenance branch will have further releases made from it. Regards, Martin ___ python-committers mailing list python-committers@python.org

Re: [python-committers] Untabifying the C codebase

Barry Warsaw wrote: On May 11, 2010, at 09:20 PM, Martin v. Löwis wrote: Barry Warsaw wrote: Who remembers the Great Renaming? :) Wasn't it the /Grand/ Renaming? See Guido's link! (btw, what a great blog :). While studying this history, I ran into http://www.rmi.net/~lutz/errata-book

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

will also switch to Mercurial, so the point of using svnmerge and blocking changes becomes irrelevant for that reason, also. So in short: in less than two months. Regards, Martin (*) there still might be bug fixes applied to the 2.7 maintenance branch which also apply to the 3.x branch. I would expect

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

it's clearly out of scope for 2.6.5, IMO. Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Is 3.1 open?

What about 3.1.3, Benjamin?. I guess it is too late for 3.1.2, since the rc is out. I saw your message asking for stopping commits the 6th march, but I haven't seen another message opening the gates again... As Martin pointed out, I don't think this patch is acceptable for a bug fix release

Re: [python-committers] Frozen branches in Hg

them, as the only person who can push to the frozen branch. FWIW, it would be possible to freeze a branch also in subversion, today. As for pulling from committer branches: that would require that committers host their branches somewhere. Regards, Martin

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

Barry Warsaw wrote: Martin, do you magic! :) I have uploaded the files, and added the signatures. I have not changed the content file; the relevant data are 3b47876d4dc3ab064926345eb76a61d2 15422464 python-2.6.5rc2.amd64.msi e6b561ccf166aec5de4daa37a465e1c1 14886912 python-2.6.5rc2.msi I'll

Re: [python-committers] branches and merging

, and nobody willing to do them - everybody just wants them to be done. So people who want the Mercurial switch to happen now really need to step forward and volunteer to work on it, or else it won't happen for another year. Regards, Martin ___ python

Re: [python-committers] branches and merging

The hold-up will ultimately be the EOL extension and the updated docs now that Dirkjan has a patch for sys.mercurial. Is that patch published somewhere? I'd like to take a look. Regards, Martin ___ python-committers mailing list python-committers

Re: [python-committers] Commit access for David Malcolm

a contributor agreement. Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] [Python-Dev] On track for Python 2.6.4 final this Sunday?

That seems to argue for doing rc2 on Sunday the 18th. If I tag the release some time Saturday, you could have the binaries by Sunday right? Correct. Regards, Martin ___ python-committers mailing list python-committers@python.org http

[python-committers] Python 2.6.4?

It seems logging is broken in 2.6.3. Should we release 2.6.4 quickly? http://bugs.python.org/issue7052 Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Python 2.6.4?

. The final 2.6.3 release mistakenly identifies its svn tag as 263rc1. It still actually is the final release, as can be seen when looking at sys.version_info. Regards, Martin ___ python-committers mailing list python-committers@python.org http

Re: [python-committers] Python 2.6.4?

Yes, but what I experienced is much worse - I was actually getting the 2.6.2 version of python26.dll due to shadowing, instead of the 2.6.3 version. Ah. Did you get a message [TARGETDIR] exists. Are you sure you want to overwrite existing files? Regards, Martin

Re: [python-committers] [PSF-Board] Mysterious uidNNN committers

database, for that matter. Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Python 2.6.2

Barry Warsaw wrote: On Apr 16, 2009, at 12:34 AM, Martin v. Löwis wrote: I've merged this into release26-maint in r71639. But in order to update Python2.6.2 binary, I think Martin's help is needed. Could you? I won't be re-releasing 2.6.2. We should make a 2.6.3 release instead. Agreed

Re: [python-committers] Python 2.6.2

this was incorrect. Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

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

s...@pobox.com wrote: Martin My own personal experience tells me git and bzr are much worse Martin than subversion (each in different respects). Perhaps you could relay these shortcomings to Brett or edit them into the PEP directly. As I said: I refrain from commenting at this point

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

a complete specification right from the start, or else discussion will revolve around the open issues, with no conclusion. So I'd rather have the PEP suggest that we switch to bzr (say), so that I can vote that down, instead of giving options in its final form. Regards, Martin

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

don't accept word-of-mouth as a proof. My own personal experience tells me git and bzr are much worse than subversion (each in different respects). Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org

Re: [python-committers] DVCS and windows line endings.

and line endings) definitely belongs into the list of issues that need to be resolved, and I think it should be show-stopper if it isn't adequately resolved (i.e. it needs to be at least as good as CVS and subversion). Regards, Martin ___ python-committers

Re: [python-committers] DVCS and windows line endings.

dumbencode, though. Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

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

, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

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

sources). It doesn't cost anything to continue to run svn. (perhaps if all the other projects except for stackless left svn, I would ask you to volunteer some admin time into its operation). Regards, Martin ___ python-committers mailing list python

Re: [python-committers] I've got a surprise for you!

unused? Worse than that: it is broken. It can't stay up for more than 30 seconds, before some watchdog mechanism reboots it - too short for me to find out what the problem is. Regards, Martin ___ python-committers mailing list python-committers@python.org

Re: [python-committers] Luke Kenneth

Anyone who feels like biting his head off, go for it. I think as a starting point, I'll revoke his access to the tracker (although I guess he'll create a new account in response). Regards, Martin ___ python-committers mailing list python-committers

  1   2   >