Can someone please add the attached SSH 2 DSA key for me? I want to be
able to help out with the rc tomorrow while I am at work.
-Brett
id_dsa.pub
Description: Binary data
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman
On Tue, Nov 18, 2008 at 13:23, Benjamin Peterson
<[EMAIL PROTECTED]> wrote:
> On Tue, Nov 18, 2008 at 3:17 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
>> Can someone please add the attached SSH 2 DSA key for me? I want to be
>> able to help out with the rc tomorrow w
On Tue, Nov 18, 2008 at 13:47, Benjamin Peterson
<[EMAIL PROTECTED]> wrote:
> On Tue, Nov 18, 2008 at 3:40 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
>> On Tue, Nov 18, 2008 at 13:23, Benjamin Peterson
>> <[EMAIL PROTECTED]> wrote:
>>> On Tue, Nov
On Tue, Nov 18, 2008 at 15:40, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
>> Adding a second key is similar to changing the keys. That said, I don't
>> think python-committers existed when that FAQ entry was written. It's
>> really up to the folks that can add new SSH keys as to which list is
>>
On Sat, Nov 22, 2008 at 03:12, Vinay Sajip <[EMAIL PROTECTED]> wrote:
> Brett Cannon has suggested [1] that the logging package should provide an
> implementation of warnings.showwarning which redirects to logging. Here are my
> first thoughts about how this might work:
>
On Sat, Nov 22, 2008 at 17:53, Vinay Sajip <[EMAIL PROTECTED]> wrote:
> Sidnei da Silva enfoldsystems.com> writes:
>
>> I do have one suggestion for improvement: instead of requiring the
>> person to do this monkey patching, add a new 'log' action to the
>> warnings filter as described by PEP 230
On Mon, Nov 24, 2008 at 08:58, Jeremy Hylton <[EMAIL PROTECTED]> wrote:
> I wanted to ask a policy question on the bug tracker. What are we
> doing with bugs filed against Python 2.4?
> This bug http://bugs.python.org/issue1208304 reports a fd leak in
> Python 2.4, which doesn't exist in the head.
On Mon, Nov 24, 2008 at 10:02, Jeremy Hylton <[EMAIL PROTECTED]> wrote:
> On Mon, Nov 24, 2008 at 12:54 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
>> On Mon, Nov 24, 2008 at 08:58, Jeremy Hylton <[EMAIL PROTECTED]> wrote:
>>> I wanted to ask a policy quest
On Mon, Nov 24, 2008 at 10:43, Mart Somermaa <[EMAIL PROTECTED]> wrote:
>> When I looked through that list a week or so ago, I noticed that some
>> issues were obviously related to the Python distribution itself, but others
>> were appeared to be Python application problems.
>
> I looked through th
On Wed, Nov 26, 2008 at 11:24, Koenig, Gerald <[EMAIL PROTECTED]> wrote:
> Hi,
>
> This is a question about development how can python meet "OEM Ready programs".
> Right now most of python is passing that programs but not all of it.
>
> Right now some of the executable are failing some of the tests
On Fri, Nov 28, 2008 at 11:07, Mart Somermaa <[EMAIL PROTECTED]> wrote:
>> If __import__ was replaced with a version with NON compatible interface,
>> "import x.y.z" would break.
>
> But it is not. The proposed __import__(name, submodule=True) has
> a compatible interface. All tests pass with
> htt
On Sun, Nov 30, 2008 at 05:02, Mart Somermaa <[EMAIL PROTECTED]> wrote:
> Brett Cannon wrote:
>
>> The old-hands on python-dev know this is where I plug my import
>> rewrite vaporware. It will be in 3.1, and as part of it there will be
>> a new API for handling dir
Can you toss the patch into the issue tracker, Jeffrey, so that any
patch comments can be done there?
-Brett
On Sun, Nov 30, 2008 at 17:54, Jeffrey Yasskin <[EMAIL PROTECTED]> wrote:
> Tracing support shows up fairly heavily an a Python profile, even
> though it's nearly always turned off. The at
On Wed, Dec 3, 2008 at 23:36, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> I would like to merge mailing lists, now that the design and first
> implementation of Python 3000 is complete. In particular, I would
> like to merge the python-3000 mailing list back into python-dev,
> and the python-300
On Thu, Dec 4, 2008 at 12:05, Frank Wierzbicki <[EMAIL PROTECTED]> wrote:
> On Wed, Dec 3, 2008 at 10:31 AM, A.M. Kuchling <[EMAIL PROTECTED]> wrote:
>> 14:00 - 15:30
>> =
>>
>> Two tracks:
>>
>> Cross-implementation issues:
>>
>> What do the various VMs want/need from CPython to help
On Thu, Dec 4, 2008 at 13:21, Georg Brandl <[EMAIL PROTECTED]> wrote:
> Benjamin Peterson schrieb:
>> On Thu, Dec 4, 2008 at 12:52 PM, Eric Smith <[EMAIL PROTECTED]> wrote:
>>> Christian Heimes wrote:
Several people have asked about the patch and merge flow. Now that Python
3.0 is ou
On Thu, Dec 4, 2008 at 13:07, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Terry Reedy wrote:
>> and this could give some people a mis-impression, most likely negative,
>> as to the magnitude and nature of the change. Most of the code I am now
>> writing would, I believe, run with 2.5 except for prin
On Fri, Dec 5, 2008 at 10:36, Georg Brandl <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> to facilitate discussion about porting Python code between different versions
> (mainly of course from 2.x to 3.x), we've created a new mailing list
>
> [EMAIL PROTECTED]
>
> It is a public mailing list open to ev
On Fri, Dec 5, 2008 at 11:20, Mark Dickinson <[EMAIL PROTECTED]> wrote:
> On Thu, Dec 4, 2008 at 3:12 PM, Christian Heimes <[EMAIL PROTECTED]> wrote:
>> Flow diagram
>>
>>
>> trunk ---> release26-maint
>> \-> py3k ---> release30-maint
>>
>
> I'm running into problems m
On Fri, Dec 5, 2008 at 22:03, <[EMAIL PROTECTED]> wrote:
> On 01:47 am, [EMAIL PROTECTED] wrote:
>>>
>>> In spite of Python being a programming language, there is a difference
>>> between 'casual user of the language' and 'library developer'; 3.0 is
>>> certainly a must for all actual library deve
On Thu, Dec 4, 2008 at 17:02, Frank Wierzbicki <[EMAIL PROTECTED]> wrote:
> On Thu, Dec 4, 2008 at 3:16 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
>> On Thu, Dec 4, 2008 at 12:05, Frank Wierzbicki <[EMAIL PROTECTED]> wrote:
>>> On Wed, Dec 3, 2008 at 10:31
On Sat, Dec 6, 2008 at 15:41, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Dec 6, 2008, at 6:25 PM, Guido van Rossum wrote:
>
>> On Sat, Dec 6, 2008 at 3:18 PM, Benjamin Peterson
>> <[EMAIL PROTECTED]> wrote:
>>>
>>> Since the release of 3.0, seve
On Mon, Dec 8, 2008 at 05:11, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Dec 7, 2008, at 7:56 PM, Christian Heimes wrote:
>
>> Barry Warsaw wrote:
>>>
>>> I'm personally okay with performance fixes in point releases, as long it
>>> doesn't chang
On Mon, Dec 8, 2008 at 18:53, A.M. Kuchling <[EMAIL PROTECTED]> wrote:
> On Sat, Dec 06, 2008 at 02:42:38PM -0800, Brett Cannon wrote:
>> No, I am saying I had told AMK I was interested in championing the
>> session. He chose you, and that's that. One less thin
On Mon, Dec 15, 2008 at 00:20, Georg Brandl wrote:
> Jeffrey Yasskin schrieb:
>> On Sun, Dec 14, 2008 at 8:26 AM, Guido van Rossum wrote:
>>> On Sat, Dec 13, 2008 at 2:11 PM, Antoine Pitrou wrote:
Guido van Rossum python.org> writes:
>
> I think we should not do this. We should use
On Fri, Dec 19, 2008 at 13:43, Fabio Zadrozny wrote:
> Hi,
>
> I'm currently having problems to get the output of Python 3.0 into the
> Eclipse console (integrating it into Pydev).
>
> The problem appears to be that stdout and stderr are not running
> unbuffered (even passing -u or trying to set P
On Sat, Dec 20, 2008 at 13:45, Fabio Zadrozny wrote:
> It appears that this bug was already reported:
> http://bugs.python.org/issue4705
>
> Any chance that it gets in the next 3.0.x bugfix release?
>
> Just as a note, if I do: sys.stdout._line_buffering = True, it also
> works, but doesn't seem
On Tue, Dec 23, 2008 at 08:00, Paul Moore wrote:
> 2008/12/23 Nick Coghlan :
>> Finding a loader given only a pseudo-filename and no module is actually
>> possible in the specific case of zipimport, but is still pretty obscure
>> at this point in time:
>>
>> 1. Scan sys.path looking for an entry t
On Tue, Dec 23, 2008 at 09:59, Mike Coleman wrote:
> I was thrown by the "Failed to find the necessary bits to build these
> modules" message at the end of newer Python builds, and thought that
> this indicated that the Python executable itself was not built.
> That's arguably stupidity on my part
On Wed, Dec 31, 2008 at 07:11, Antoine Pitrou wrote:
>
> Hi,
>
> Stephen J. Turnbull xemacs.org> writes:
>>
>> There *is* a process problem, though I don't claim to have an idea how
>> to solve it. Some developers (especially well-known is Martin van
>> Loewis) are trying to address this with th
On Tue, Dec 30, 2008 at 16:55, Victor Stinner
wrote:
> Hi,
>
> I already asked in September to get an svn account to be able to commit
> directly patches to trunk (or other branches like py3k). My query was
> rejected because I didn't know Python core enough (and maybe other reasons
> that I don't
On Fri, Jan 2, 2009 at 18:53, Victor Stinner
wrote:
> Le Wednesday 31 December 2008 22:20:54, vous avez écrit :
>> When it comes to commit privs in general, I am of the school that they
>> should be handed out carefully. I for one do not want to have to
>> babysit other committers to make sure tha
On Sat, Jan 3, 2009 at 00:50, "Martin v. Löwis" wrote:
>> A little offtopic: it seems to me it is a flaw of svn, that it
>> encourages the model of two classes of developers, those with a commit
>> access (first class) and those without it (second class). Victor --
>> maybe you can try something l
On Sat, Jan 3, 2009 at 10:42, Barry Warsaw wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Jan 3, 2009, at 11:36 AM, Martin v. Löwis wrote:
>
>> We can setup such a branch, unless you reconsider and try bazaar first.
>> There wouldn't be any pushing it back upstream, though - you w
On Sat, Jan 3, 2009 at 09:52, Georg Brandl wrote:
> Steve Holden schrieb:
>
>> I think it was courageous of Brett to tackle this issue head-on as he
>> did, and of Victor to respond so positively to the various comments that
>> have been made on this thread. It would be a pity to lose a developer
On Sat, Jan 3, 2009 at 14:17, "Martin v. Löwis" wrote:
>> I have been using bzr for all of my importlib work. It's worked out
>> well sans the problem that SOMEONE Barry has not
>> upgraded the bzr installation to support the newest wire protocol.
>
> I'm probably to blame for this. Debian doesn't
On Sat, Jan 3, 2009 at 14:47, "Martin v. Löwis" wrote:
>>> As a consequence, I would always request that whatever VCS Python
>>> uses: the version that is in the current Debian's "stable" distribution
>>> must be sufficient to use the VCS, and must in particular be sufficient
>>> on the server sid
On Sat, Jan 3, 2009 at 15:21, Ivan Krstić
wrote:
> On Jan 3, 2009, at 5:47 PM, Martin v. Löwis wrote:
>>
>> There have been many problems on upgrade for the cases where we gave in:
>> shared libraries were missing after the upgrade (for Zope), the software
>> wasn't available anymore after the upg
On Sat, Jan 3, 2009 at 16:06, "Martin v. Löwis" wrote:
>> Do any of the DVCS under consideration satisfy that requirement? I
>> guess I'm asking whether you think all this talk about DVCSes is futile
>> or premature?
>
> I still do hope that Debian releases lenny before any of this advances.
> Th
On Sat, Jan 3, 2009 at 16:39, "Martin v. Löwis" wrote:
>> Bazaar has been backwards-compatible with everything from my
>> understanding, so any changes they have made to the repository layout
>> or network protocol they use should not be an issue regardless of what
>> client or server versions are
On Mon, Jan 5, 2009 at 23:13, Simon Cross wrote:
> If there's going to be another bug day, I'd like to see the problem of
> getting patches from the bug tracker into Python addressed in some
> way. It's kinda frustrating to work on things and not actually get to
> close any issues because there a
On Wed, Jan 7, 2009 at 10:57, M.-A. Lemburg wrote:
[SNIP]
> BTW: The _codecsmodule.c file is a 4 spaces indent file as well (just
> like all Unicode support source files). Someone apparently has added
> tabs when adding support for Py_buffers.
>
It looks like this formatting mix-up is just going
On Thu, Jan 8, 2009 at 01:52, Raymond Hettinger wrote:
> From: "M.-A. Lemburg"
>>
>> The question to put up against this is: How often do you get
>> irritated by lines not being correctly indented ?
>
> Basically never.
And of course I am the polar opposite: frequently enough that I want
to see
On Thu, Jan 8, 2009 at 10:41, Guido van Rossum wrote:
> On Thu, Jan 8, 2009 at 10:29 AM, Brett Cannon wrote:
>> On Thu, Jan 8, 2009 at 01:52, Raymond Hettinger wrote:
>>> From: "M.-A. Lemburg"
>>>>
>>>> The question to put up against this
My work rewriting import in pure Python code has reached beta.
Basically the code is semantically complete and as
backwards-compatible as I can make it short of widespread testing or
running on a Windows box. There are still some tweaks here and there I
want to make and an API to expose, but __impo
So it turns out that if you try to do a relative import where a parent
is not loaded, it raises a SystemError. This has been in there since
Guido added package support back in the day. But this seems more like
an ImportError than a SystemError to me. My guess is that the original
purpose was to sig
On Thu, Jan 8, 2009 at 11:26, Paul Moore wrote:
> 2009/1/8 Brett Cannon :
>> My work rewriting import in pure Python code has reached beta.
>> Basically the code is semantically complete and as
>> backwards-compatible as I can make it short of widespread testing or
>&g
On Thu, Jan 8, 2009 at 11:33, Guido van Rossum wrote:
> On Thu, Jan 8, 2009 at 11:25 AM, Brett Cannon wrote:
>> So it turns out that if you try to do a relative import where a parent
>> is not loaded, it raises a SystemError. This has been in there since
>> Guido added pa
On Thu, Jan 8, 2009 at 12:43, Nick Coghlan wrote:
> Brett Cannon wrote:
>> Can we then all agree that a policy of re-indenting per function as
>> changes are made to the code is acceptable but not required?
>
> Such a rule would certainly make *my* life a lot easier - the rea
On Thu, Jan 8, 2009 at 12:35, Nick Coghlan wrote:
> Brett Cannon wrote:
>> One, does anyone have issues if I check in importlib? We have
>> typically said code has to have been selected as best-of-breed by the
>> community first, so I realize I am asking for a waiver on th
On Thu, Jan 8, 2009 at 12:57, Paul Moore wrote:
> 2009/1/8 Brett Cannon :
>> Thanks, Paul! I changed it to _os.getcwd() since that's what nt exposes.
>
> Ta. I wasn't sure _os.getcwd() returned a full pathname.
>
> The only difference between the importlib results
On Thu, Jan 8, 2009 at 13:14, Antoine Pitrou wrote:
> Brett Cannon python.org> writes:
>>
>> One, does anyone have issues if I check in importlib? We have
>> typically said code has to have been selected as best-of-breed by the
>> community first, so I realize I
On Thu, Jan 8, 2009 at 13:21, Nick Coghlan wrote:
> Brett Cannon wrote:
>> On Thu, Jan 8, 2009 at 12:35, Nick Coghlan wrote:
>>> Brett Cannon wrote:
>>>> One, does anyone have issues if I check in importlib? We have
>>>> typically said code has to
On Thu, Jan 8, 2009 at 17:31, Benjamin Peterson wrote:
> On Thu, Jan 8, 2009 at 2:52 PM, Brett Cannon wrote:
>> On Thu, Jan 8, 2009 at 12:43, Nick Coghlan wrote:
>>>
>>> Even if we do adopt such a rule, C patches posted to the tracker should
>>> still tr
On Thu, Jan 8, 2009 at 17:42, Benjamin Peterson wrote:
> On Thu, Jan 8, 2009 at 7:39 PM, Brett Cannon wrote:
>> On Thu, Jan 8, 2009 at 17:31, Benjamin Peterson wrote:
>>> On Thu, Jan 8, 2009 at 2:52 PM, Brett Cannon wrote:
>>>> On Thu, Jan 8, 2009
On Fri, Jan 9, 2009 at 09:50, Benjamin Peterson wrote:
> This is just a note that the PEP index (PEP 0) is now automatically
> generated, so you need not bother to update any more.
Thanks for getting this done!
-Brett
___
Python-Dev mailing list
Python
be run by regrtest, and then check the code in! I am going to
set PyCon as a hard deadline such that no matter how much more file
churn I have left I will still check it into py3k by then (along with
importlib.import_module() into 2.7).
On Thu, Jan 8, 2009 at 11:06, Brett Cannon wrote:
> My w
On Tue, Jan 13, 2009 at 06:09, Kristján Valur Jónsson
wrote:
> By accident i had a dir called @test in my PCBuild directory when I was
> running the testsuite.
>
> This caused the test_support to define TESTFN as tmp/@test.
>
>
>
> This again caused a number of tests to fail. One issue I have alr
On Fri, Jan 16, 2009 at 13:34, Mark Dickinson wrote:
> Now that all uses of nb_long and __long__ have disappeared from
> the 3.x codebase, would it make sense to mark PyNumber_Long
> as deprecated in the c-api documentation, and convert all existing
> uses (I count a grand total of 3 uses in the p
I just realized that I had not received any emails on python-checkins
about the buildbot failures I accidentally caused. And then I noticed
that I had not gotten any emails for py3k in a while. Did that get
switched off on purpose?
-Brett
___
Python-Dev
On Sun, Jan 18, 2009 at 01:53, "Martin v. Löwis" wrote:
> Brett Cannon wrote:
>> I just realized that I had not received any emails on python-checkins
>> about the buildbot failures I accidentally caused. And then I noticed
>> that I had not gotten any emails fo
On Sun, Jan 18, 2009 at 14:22, "Martin v. Löwis" wrote:
>
>> All I know is that I checked in a test that failed on all
>> case-sensitive file system for py3k (3.1) and there does not appear to
>> be a single email about it. And the buildbots very clearly had the
>> chance to fail.
>
> What is the
On Sun, Jan 18, 2009 at 14:49, "Martin v. Löwis" wrote:
>>> What is the specific checkin? What specific builds failed?
>>>
>>
>> How about one that just happened:
>> http://www.python.org/dev/buildbot/3.x.stable/sparc%20solaris10%20gcc%203.x/builds/126
>> . If you look at the python-checkins for t
On Sun, Jan 18, 2009 at 15:03, Antoine Pitrou wrote:
> Dear python-dev,
>
> The Python implementation of IOBase, the base class for everything IO, has the
> (strange) idea to define a __del__ method. It is probably meant to avoid code
> duplication, so that users subclassing IOBase automatically g
On Mon, Jan 19, 2009 at 10:03, Gerald Britton wrote:
> Duly noted and thanks for the feedback! (just what I was looking for
> actually). I do disagree with the idea that the proposal, if
> implemented, would make Python harder to learn. Not sure who would
> find it harder. Having to find and u
I have been writing up the initial docs for importlib and four things struck me:
1. Why is three space indents the preferred indentation level?
2. Should we start using function annotations?
3. Are brackets for optional arguments (e.g. ``def fxn(a [, b=None [,
c=None]])``) really necessary when
On Mon, Jan 19, 2009 at 19:01, Benjamin Peterson wrote:
> On Mon, Jan 19, 2009 at 8:24 PM, Brett Cannon wrote:
>> I have been writing up the initial docs for importlib and four things struck
>> me:
>>
>> 1. Why is three space indents the preferred indentation le
On Mon, Jan 19, 2009 at 19:19, Benjamin Peterson wrote:
> On Mon, Jan 19, 2009 at 9:11 PM, Brett Cannon wrote:
>> On Mon, Jan 19, 2009 at 19:01, Benjamin Peterson wrote:
>>> On Mon, Jan 19, 2009 at 8:24 PM, Brett Cannon wrote:
>>>>
>>>> 2. Should we st
On Mon, Jan 19, 2009 at 19:50, Raymond Hettinger wrote:
> I have another question about doc formatting.
>
> What controls whether section headers get urls with a custom named jump
> target instead of a default name like "id1"?
>
> In particular, look at the urls for:
> http://docs.python.org/dev
On Mon, Jan 19, 2009 at 19:02, Scott Dial
wrote:
> Brett Cannon wrote:
>> 3. Are brackets for optional arguments (e.g. ``def fxn(a [, b=None [,
>> c=None]])``) really necessary when default argument values are
>> present? And do we really need to nest the brackets when
On Wed, Jan 21, 2009 at 13:53, Georg Brandl wrote:
> Brett Cannon schrieb:
>> I have been writing up the initial docs for importlib and four things struck
>> me:
>>
>> 1. Why is three space indents the preferred indentation level?
>
> As said, it matches directi
On Thu, Jan 22, 2009 at 10:12, Georg Brandl wrote:
> Brett Cannon schrieb:
>
>>>> 3. Are brackets for optional arguments (e.g. ``def fxn(a [, b=None [,
>>>> c=None]])``) really necessary when default argument values are
>>>> present? And do we really ne
I have now converted PEP 374
(http://www.python.org/dev/peps/pep-0374/) from Google Docs to reST
and checked it in. I am not going to paste it into an email as it is
nearly 1500 lines in reST form.
Because there are four authors handling corrections it is a little
different than normal on who you
On Fri, Jan 23, 2009 at 00:31, "Martin v. Löwis" wrote:
> Giampaolo Rodola' wrote:
>> Hi,
>> while attempting to port pyftpdlib [1] to Python 3 I have noticed that
>> ftplib differs from the previous 2.x version in that it uses latin-1
>> to encode everything it's sent over the FTP command channel
On Fri, Jan 23, 2009 at 00:39, "Martin v. Löwis" wrote:
>> And I would like to thank my co-authors for their time and effort thus
>> far in filling in the PEP on behalf of their favorite DVCS. Everyone
>> has put in a lot of time already with I am sure more time in the
>> future.
>
> So what will
On Fri, Jan 23, 2009 at 03:05, Antoine Pitrou wrote:
> Brett Cannon python.org> writes:
>>
>> I have now converted PEP 374
>> (http://www.python.org/dev/peps/pep-0374/) from Google Docs to reST
>> and checked it in. I am not going to paste it into an email as it i
On Fri, Jan 23, 2009 at 07:30, Barry Warsaw wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Brett, thanks for putting this PEP together!
>
Yep. Just make sure I don't do something like this for a LONG time.
Apparently I didn't learn my lesson after the issue tracker migration.
> On
Uh, Tony, I think you sent this to the wrong email address. =)
On Fri, Jan 23, 2009 at 11:22, Tony Lownds wrote:
> Rob and/or Tim,
> Can you track this down?
> Thanks
> -Tony
>
> Begin forwarded message:
>
> From: support+...@pagedna.com
> Date: January 23, 2009 11:16:26 AM PST
> To: probl...@pa
On Fri, Jan 23, 2009 at 12:11, Steven Bethard wrote:
> On Fri, Jan 23, 2009 at 12:06 PM, "Martin v. Löwis"
> wrote:
>>> import random
>>> print(random.choice('svn', 'bzr', 'hg', 'git'))
>>
>> Nice! So it's bzr, as my machine just told me (after adding
>> the square brackets).
>
> Wow, th
On Fri, Jan 23, 2009 at 13:39, Paul Moore wrote:
> 2009/1/23 "Martin v. Löwis" :
>>> Brett mentioned in his email that he wasn't ready to make a decision yet, I
>>> think? I also think that the PEP could still use some modifications from
>>> people
>>> who have more experience with the DVCSs.
>>
On Sat, Jan 24, 2009 at 07:25, Aahz wrote:
> On Thu, Jan 22, 2009, Brett Cannon wrote:
>>
>> I have now converted PEP 374
>> (http://www.python.org/dev/peps/pep-0374/) from Google Docs to reST
>> and checked it in.
>
> First of all, thanks for providing PEP num
On Sat, Jan 24, 2009 at 15:34, "Martin v. Löwis" wrote:
>>> Second, I think it would be good to explicitly mention the option of
>>> deferring this PEP. Based on previous discussion, it sounds like there
>>> are a fair number of people who think that there is a DVCS in Python's
>>> future, but no
On Sat, Jan 24, 2009 at 16:44, Nick Coghlan wrote:
> Brett Cannon wrote:
>> On Sat, Jan 24, 2009 at 15:34, "Martin v. Löwis" wrote:
>>>>> Second, I think it would be good to explicitly mention the option of
>>>>> deferring this PEP. Based on prev
On Sat, Jan 24, 2009 at 14:46, Raymond Hettinger wrote:
> I would like to deprecate some outdated functions in the operator module.
>
> The isSequenceType(), isMappingType(), and isNumberType()
> functions never worked reliably and now their
> intended purpose has been largely fulfilled by
> ABCs.
On Sun, Jan 25, 2009 at 10:37, "Martin v. Löwis" wrote:
>> There's a possible third way. I've heard (though haven't investigated)
>> that some people are working on supporting the svn wire protocol in the
>> bzr server. This would mean that anybody who's still comfortable with
>> svn and feels n
On Sun, Jan 25, 2009 at 13:03, Michael Foord wrote:
> Brett Cannon wrote:
>>
>> On Sun, Jan 25, 2009 at 10:37, "Martin v. Löwis"
>> wrote:
>>
>>>>
>>>> There's a possible third way. I've heard (though haven't investigat
On Tue, Jan 27, 2009 at 11:29, Barry Warsaw wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Jan 27, 2009, at 2:05 PM, Guido van Rossum wrote:
>
>> On Tue, Jan 27, 2009 at 11:00 AM, Raymond Hettinger
>> wrote:
>>>
>>> With the extensive changes in the works, Python 3.0.1 is shaping
On Tue, Jan 27, 2009 at 14:31, "Martin v. Löwis" wrote:
>> My preference is to drop 3.0 entirely (no incompatable bugfix release)
>> and in early February release 3.1 as the real 3.x that migrators ought
>> to aim for and that won't have incompatable bugfix releases. Then at
>> PyCon, we can have
On Tue, Jan 27, 2009 at 14:44, Antoine Pitrou wrote:
> Raymond Hettinger rcn.com> writes:
>>
>> What is involved in finishing io-in-c?
>
> Off the top of my head:
> - fix the _ssl bug which prevents some tests from passing (issue #4967)
> - clean up io.py (and decide what to do with the remaining
On Thu, Jan 29, 2009 at 02:38, Dr Andrew Perella wrote:
> Hi,
>
> I was thinking of adding a breakpoint opcode to python to enable less
> invasive debugging.
>
> I came across posts from 1999 by Vladimir Marangozov and Christian Tismer
> discussing this issue but the links to the code are all out
On Thu, Jan 29, 2009 at 12:39, Christopher Barker wrote:
> Hi all,
>
> Over on the matplotlib mailing list, we ran into a problem with trying to
> use Universal newlines with gzip. In virtually all of my code that reads
> text files, I use the 'U' flag to open files, it really helps not having to
On Thu, Jan 29, 2009 at 18:27, "Martin v. Löwis" wrote:
>> There are potential problems with doing it that way [1]. The safer
>> option is to do:
>>
>> svn revert .
>> svnmerge merge -M -F
>
> I still don't see the potential problem. If you do svnmerge, svn commit,
> all is fine, right? The probl
On Thu, Jan 29, 2009 at 19:03, "Martin v. Löwis" wrote:
> Brett Cannon wrote:
>> On Thu, Jan 29, 2009 at 18:27, "Martin v. Löwis" wrote:
>>>> There are potential problems with doing it that way [1]. The safer
>>>> option is to do:
>>
This is my attempt to summarize what everyone has been saying so we
can get this resolved.
>From what I can tell, most people like the idea of doing a 3.0.1
release ASAP (like "in a week or so" fast) with the stuff that should
have been removed from 3.0.0 in the first place removed.
People also s
On Fri, Jan 30, 2009 at 08:03, Barry Warsaw wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Jan 30, 2009, at 12:53 AM, Martin v. Löwis wrote:
>
>>> 1. Barry, who is the release manager for 3.0.1, does not like the idea
>>> of the cruft that is being proposed removed from 3.0.1.
>>
On Fri, Jan 30, 2009 at 12:07, Benjamin Peterson wrote:
> On Fri, Jan 30, 2009 at 1:56 PM, Brett Cannon wrote:
>> Great! Then should we start planning for 3.0.1 in terms of release
>> dates and what to have in the release so we can get this out the door
>> quickly?
&g
On Mon, Feb 2, 2009 at 00:52, Rocky Bernstein wrote:
> As I've mentioned, I've been re-examining from ground up the whole
> state of affairs in writing a debugger.
>
> One of the challenges of a debugger or any source-code analysis tool
> is verifying that the source-code that the tool is reportin
On Tue, Feb 3, 2009 at 11:08, Brad Miller wrote:
> I'm just getting ready to start the semester using my new book (Python
> Programming in Context) and noticed that I somehow missed all the changes to
> urllib in python 3.0. ARGH to say the least. I like using urllib in the
> intro class because
On Tue, Feb 3, 2009 at 15:50, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Brett Cannon wrote:
>> On Tue, Feb 3, 2009 at 11:08, Brad Miller wrote:
>>> I'm just getting ready to start the semester using my new book (Python
>>> P
On Wed, Feb 4, 2009 at 05:35, Hrvoje Niksic wrote:
> Andrew Bennetts wrote:
>>
>> A patch to add operator.caller(*args, **kwargs) may be a good idea. Your
>> example would then be:
>>
>>map(operator.caller(), lst)
>
> Regarding the name, note that I proposed operator.call (and
> operator.__ca
2601 - 2700 of 3314 matches
Mail list logo
