On Wed, Sep 29, 2010 at 11:41, Antoine Pitrou wrote:
> On Wed, 29 Sep 2010 11:32:19 -0700
> Guido van Rossum wrote:
>> I would like to recommend that the Python core developers start using
>> a code review tool such as Rietveld or Reviewboard. I don't really
>> care which tool we use (I'm sure th
On Wed, Sep 29, 2010 at 12:03, Guido van Rossum wrote:
> On Wed, Sep 29, 2010 at 11:47 AM, Brett Cannon wrote:
>> On Wed, Sep 29, 2010 at 11:41, Antoine Pitrou wrote:
>>> On Wed, 29 Sep 2010 11:32:19 -0700
>>> Guido van Rossum wrote:
>>>> I would
On Wed, Sep 29, 2010 at 13:23, Guido van Rossum wrote:
> On Wed, Sep 29, 2010 at 1:12 PM, Brett Cannon wrote:
>> On Wed, Sep 29, 2010 at 12:03, Guido van Rossum wrote:
>>> A problem with that is that we regularly make matching improvements to
>>> upload.py and the s
On Wed, Sep 29, 2010 at 13:31, Alexander Belopolsky
wrote:
> On Wed, Sep 29, 2010 at 4:23 PM, Guido van Rossum wrote:
> ..
>> But maybe with Hg it's less of a burden to ask people to use a checkout.
>>
>
> I thought with Hg it would be more of a burden for casual contributors
> to use a checkout
On Wed, Sep 29, 2010 at 13:43, Antoine Pitrou wrote:
> Le mercredi 29 septembre 2010 à 13:35 -0700, Brett Cannon a écrit :
>>
>> Well, we can start with strongly worded suggestions that patches
>> submitted using Rietveld will typically get priority over patches
>>
On Wed, Sep 29, 2010 at 14:35, "Martin v. Löwis" wrote:
>> While I would personally love to see Rietveld declared the official
>> core Python code review tool, I realize that since I wrote as a Google
>> engineer and it is running on Google infrastructure (App Engine), I
>> can't be fully objectiv
On Wed, Sep 29, 2010 at 14:58, "Martin v. Löwis" wrote:
>> That shouldn't be too hard. Someone just has to create an App Engine
>> project and handle the deployment. I guess the trickiest part is
>> making sure enough people have admin access so multiple people can
>> update the website, especiall
On Wed, Sep 29, 2010 at 15:15, "Martin v. Löwis" wrote:
>> I don't know how hg manages this, but can't we preserve the tag
>> information of the tags that you've scheduled to be removed
>> in some place that can easily be pulled in but doesn't
>> affect the main repo size ?
>
> Most certainly, and
On Thu, Sep 30, 2010 at 08:31, Daniel Stutzbach
wrote:
> On Thu, Sep 30, 2010 at 9:52 AM, wrote:
>>
>> Of course, this is only true if the core developers *do* submit to the
>> same rules. Is anyone proposing that current core committers have all their
>> work reviewed before it is accepted?
>
>
On Thu, Sep 30, 2010 at 09:19, Georg Brandl wrote:
> Am 29.09.2010 20:49, schrieb Guido van Rossum:
>
>> Unfortunately taking the average patch posted to the tracker and
>> importing it in Rietveld is very iffy -- it's very hard to find the
>> right branch+rev needed to be able to apply the patch
It's best to report issues at bugs.python.org.
On Thu, Oct 7, 2010 at 05:17, Thomas Klausner wrote:
> Hi!
>
> I'm running newspipe-1.1.9, an RSS reader
> (http://newspipe.sourceforge.net/), on NetBSD-5.99.11/amd64 using
> Python-2.6.6.
>
> Sometimes, it core dumps with particular feeds in the con
On Thu, Oct 7, 2010 at 15:53, Thomas Klausner wrote:
> On Thu, Oct 07, 2010 at 11:15:27AM -0700, Brett Cannon wrote:
>> It's best to report issues at bugs.python.org.
>
> Are different people reading it there?
Yes, but we also just don't accept bug reports here as they
On Fri, Oct 8, 2010 at 09:25, Tarek Ziadé wrote:
> On Fri, Oct 8, 2010 at 5:53 PM, Toshio Kuratomi wrote:
>> On Fri, Oct 08, 2010 at 05:12:44PM +0200, Antoine Pitrou wrote:
> ...
>>> > pysetup is shorter
>
> Let's use pysetup !
>
> ...
>> I won't bikeshed as long as we stay away from conflicting
On Fri, Oct 8, 2010 at 14:44, Tarek Ziadé wrote:
> On Fri, Oct 8, 2010 at 9:31 PM, Brett Cannon wrote:
>> On Fri, Oct 8, 2010 at 09:25, Tarek Ziadé wrote:
>>> On Fri, Oct 8, 2010 at 5:53 PM, Toshio Kuratomi wrote:
>>>> On Fri, Oct 08, 2010 at 05:12:44
Doesn't autoconf need to be run to regenerate configure?
On Thu, Oct 14, 2010 at 08:24, matthias.klose
wrote:
> Author: matthias.klose
> Date: Thu Oct 14 17:24:22 2010
> New Revision: 85481
>
> Log:
> - Issue #10094: Use versioned .so files on GNU/kfreeBSD and the GNU Hurd.
>
>
> Modified:
> py
On Thu, Oct 14, 2010 at 02:25, Antoine Pitrou wrote:
>
> Hello,
>
> In the http://bugs.python.org/issue10093 discussion, I proposed to add a
> specific warning category for unclosed files. The rationale is that
> these warnings will happen in destructors and therefore filtering by
> line number an
On Fri, Oct 15, 2010 at 03:27, Nick Coghlan wrote:
> On Fri, Oct 15, 2010 at 7:44 PM, Michael Foord
> wrote:
>> On 15/10/2010 08:22, Stephen J. Turnbull wrote:
>>>
>>> Brett Cannon writes:
>>>
>>> > As one of the co-authors of the PEP I say
On Thu, Oct 21, 2010 at 06:32, Dirkjan Ochtman wrote:
> Okay, we're getting somewhere here.
>
> I've been conferring with Georg on when we can do the conversion. He's
> done some testing with the buildbot setup, which seems to be mostly
> done. He also completed preliminary ports of the hooks used
On Fri, Oct 22, 2010 at 09:26, Georg Brandl wrote:
> Am 19.10.2010 17:24, schrieb P.J. Eby:
>> At 08:03 AM 10/18/2010 +1000, Nick Coghlan wrote:
>>>I'm a little dubious about exposing these officially. They're mainly a
>>>hack to get some parts of the standard library working (e.g. runpy) in
>>>th
Can whomever has edit access to the Python Google Calendar add this?
On Mon, Oct 25, 2010 at 14:03, Antoine Pitrou wrote:
>
> Hello,
>
> The development team of the Python interpreter (a.k.a python-dev) is
> organizing a bug week-end on Saturday 20th and Sunday 21st of November.
>
> We would like
2010/10/28 Kristján Valur Jónsson :
> Hi all.
> This has been a lively discussion.
> My desire to keep 2.x alive in some sense is my own and I don't know if
> anyone shares it but as a member of this community I think I'm allowed to
> voice it. So, just to clarify my particular position, let me
For those of you who have not noticed, Antoine committed a patch that
raises a ResourceWarning under a pydebug build if a file or socket is
closed through garbage collection instead of being explicitly closed.
I have started to go through the test suite to fix as many of these
cases as possible, b
2010/11/1 Kristján Valur Jónsson :
> I've been sitting on the sideline seeing this unfold.
> We've seen some different viewpoints on the matter and I'm happy to see that
> I'm not the only one lamenting the proclaimed death of the 2.x linage.
> However, As correctly stated by Martin, I merely voic
On Wed, Oct 27, 2010 at 03:42, Antoine Pitrou wrote:
> On Tue, 26 Oct 2010 22:06:37 -0400
> Alexander Belopolsky wrote:
>>
>> While I appreciate your and Michael's eloquence, I don't really see
>> why five 400-line modules are necessarily easier to maintain than one
>> 2000-line module. Splittin
On Tue, Nov 2, 2010 at 15:33, Nick Coghlan wrote:
> On Tue, Nov 2, 2010 at 12:35 PM, Brett Cannon wrote:
>> So basically it seems like we have learned a lesson: we prefer to have
>> our code structured in files that match the public API. I think that
>> is a legitimate desig
On Tue, Nov 2, 2010 at 15:47, Raymond Hettinger
wrote:
> On Nov 1, 2010, at 7:35 PM, Brett Cannon wrote:
>
> I think the issue here is that the file structure of the code no
> longer matches the public API documented by unittest. Personally I,
> like most people it seems, prefer
On Tue, Nov 2, 2010 at 16:43, Guido van Rossum wrote:
> On Tue, Nov 2, 2010 at 4:39 PM, Michael Foord
> wrote:
>> As the maintainer of unittest I'd like to say that in the absence of clear
>> consensus that the merger should happen, or a fiat from the BDFL, the merger
>> won't happen. I believe
On Tue, Nov 2, 2010 at 17:35, Guido van Rossum wrote:
> If you are importing the code, the __module__ attribute on each class
> should tell you where it is actually defined (as opposed to where you
> imported it from). Then sys.modules gives you the module object which
> has a __file__ attribute,
On Tue, Nov 2, 2010 at 19:50, Michael Foord wrote:
> On 02/11/2010 02:35, Brett Cannon wrote:
>>
>> On Wed, Oct 27, 2010 at 03:42, Antoine Pitrou wrote:
>>>
>>> On Tue, 26 Oct 2010 22:06:37 -0400
>>> Alexander Belopolsky wrote:
>>>>
>>
On Mon, Nov 8, 2010 at 04:09, Michael Foord wrote:
> Hello all,
>
> Now that unittest has test discovery, Mark Roddy has been working on
> resurrecting the old GUI test runner (using Tkinter):
>
> https://bitbucket.org/markroddy/unittestgui
>
> This was part of the original pyunit project but I be
On Mon, Nov 8, 2010 at 09:20, Alexander Belopolsky
wrote:
> Was: [issue2001] Pydoc interactive browsing enhancement
>
> On Sun, Nov 7, 2010 at 9:17 AM, Nick Coghlan wrote:
> ..
>>
>> I'd actually started typing out the command to commit this before it finally
>> clicked that the patch changes pu
On Mon, Nov 8, 2010 at 13:03, wrote:
> On 07:58 pm, br...@python.org wrote:
>>>
>>> I don't think a strict don't remove without deprecation policy is
>>> workable. For example, is trace.rx_blank constant part of the trace
>>> module API that needs to be preserved indefinitely? I don't even know
On Mon, Nov 8, 2010 at 13:45, wrote:
> On 09:25 pm, br...@python.org wrote:
>>
>> On Mon, Nov 8, 2010 at 13:03, wrote:
>>>
>>> On 07:58 pm, br...@python.org wrote:
>
> I don't think a strict don't remove without deprecation policy is
> workable. For example, is trace.rx_blank const
On Mon, Nov 8, 2010 at 13:36, Ron Adam wrote:
>
>
> On 11/08/2010 01:58 PM, Brett Cannon wrote:
>>
>> On Mon, Nov 8, 2010 at 09:20, Alexander Belopolsky
>> wrote:
>>>
>>> Was: [issue2001] Pydoc interactive browsing enhancement
>>>
>&
On Mon, Nov 8, 2010 at 16:10, Ron Adam wrote:
>
>
> On 11/08/2010 04:01 PM, Brett Cannon wrote:
>
>>> My understanding is that anything with an actual docstring is part of the
>>> public API. Any thing with a leading underscore is private.
>>
>> Tha
On Wed, Nov 10, 2010 at 05:47, Michael Foord wrote:
> On 08/11/2010 22:07, Raymond Hettinger wrote:
>>
>> On Nov 8, 2010, at 11:58 AM, Brett Cannon wrote:
>>
>>> I think we need to, as a group, decide how to handle undocumented APIs
>>> that don't have
On Thu, Nov 11, 2010 at 09:38, Éric Araujo wrote:
>>> Shouldn’t this include an entry in NEWS and maybe in ACKS?
>> It was a very simple bug fix (caused due to an overlook initially), so
>> did not add NEWS/ACKS. For features, larger fixes or complete patches,
>> I the add NEWS and ACKS as appropr
On Thu, Nov 11, 2010 at 10:10, Éric Araujo wrote:
>> I just follow Guido's own personal rule: if the fix required thought
>> they should go into Misc/ACKS.
>
> Okay. Same rule for NEWS?
>
>
I do a NEWS entry if a bug was fixed or semantics changed/added for
anything public (e.g., I don't do an e
On Fri, Nov 19, 2010 at 05:50, Nick Coghlan wrote:
> On Fri, Nov 19, 2010 at 5:43 PM, Georg Brandl wrote:
>> Am 19.11.2010 03:23, schrieb Benjamin Peterson:
>>> 2010/11/18 Jesus Cea :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/11/10 18:32, "Martin v. Löwis" wrote:
>>>
On Mon, Nov 22, 2010 at 10:34, Jesus Cea wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> A Solaris installation contains ALWAYS 32 and 64 bits libraries. So in
> any Solaris you can run 32/64 bits programs, and compile in 32 and 64 bits.
>
> For this, libraries are stores in "/usr/lib
On Mon, Nov 22, 2010 at 10:58, Ezio Melotti wrote:
> On 22/11/2010 19.45, Michael Foord wrote:
>>
>> On 22/11/2010 17:35, Łukasz Langa wrote:
>>>
>>> Am 22.11.2010 18:14, schrieb Ezio Melotti:
I would like to re-enable by default warnings for regrtest and/or
unittest.
>>>
>>> +1
>>>
On Mon, Nov 22, 2010 at 13:08, Guido van Rossum wrote:
> On Mon, Nov 22, 2010 at 11:24 AM, Brett Cannon wrote:
>> The problem with that is it means developers who switch to Python 3.2
>> or whatever are suddenly going to have their tests fail until they
>> update their code
On Tue, Nov 23, 2010 at 15:07, Terry Reedy wrote:
>
>
> On 11/23/2010 5:43 PM, Éric Araujo wrote:
>>>
>>> Modified: python/branches/py3k/Misc/ACKS
>>>
>>> ==
>>> --- python/branches/py3k/Misc/ACKS (original)
>>> +++ p
On Mon, Nov 29, 2010 at 03:53, Sylvain Thénault
wrote:
> On 25 novembre 11:22, Ron Adam wrote:
>> On 11/25/2010 08:30 AM, Emile Anclin wrote:
>> >
>> >hello,
>> >
>> >working on Pylint, we have a lot of voluntary corrupted files to test
>> >Pylint behavior; for instance
>> >
>> >$ cat /home/emile/
On Mon, Nov 29, 2010 at 12:21, Ron Adam wrote:
>
>
> On 11/29/2010 01:22 PM, Brett Cannon wrote:
>>
>> On Mon, Nov 29, 2010 at 03:53, Sylvain Thénault
>> wrote:
>>>
>>> On 25 novembre 11:22, Ron Adam wrote:
>>>>
>>&
On Tue, Nov 30, 2010 at 00:34, Sylvain Thénault
wrote:
> On 29 novembre 14:21, Ron Adam wrote:
>> On 11/29/2010 01:22 PM, Brett Cannon wrote:
>> >Considering these semantics changed between Python 2 and 3 w/o a
>> >discernable benefit (I would consider it a negative as
On Tue, Nov 30, 2010 at 07:35, Barry Warsaw wrote:
> On Nov 30, 2010, at 01:09 PM, Michael Foord wrote:
>
>>PEP 291 is very old and should probably be retired. I don't think anyone is
>>maintaining standard libraries in py3k that are also compatible with Python
>>2.anything. (At least not in a sin
On 7/8/06, Talin <[EMAIL PROTECTED]> wrote:
Brett Cannon wrote:> On 7/7/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:>> On 7/8/06, Ka-Ping Yee <[EMAIL PROTECTED]
> wrote:>> > I'd like the answer to be yes. It sounded for a while like this>> >
As I am sure some have noticed, as part of my dissertation I have been trying to fix the various crashers. I currently have some patches in SF for some of the crashers. The other ones Armin and I have been talking, while others I have not started yet. Review for the patches or help with fixing t
On 7/10/06, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
Brett Cannon wrote:> As I am sure some have noticed, as part of my dissertation I have been> trying to fix the various crashers.Nice project.One quick thought: Any crasher that relies on
gc.get_referrers() shouldnot be
http://www.klocwork.com/company/releases/06_26_06.aspLooks like Klocowork is doing the same thing as Coverity and providing free static analysis of source for open source projects. Doubt we want this *and* Coverity, but figured wouldn't hurt to let people know about it.
-Brett
On 7/10/06, Talin <[EMAIL PROTECTED]> wrote:
Brett Cannon wrote:> Using a factory method callback, one could store the PyCodeObject in a C> proxy object that just acts as a complete delegate, forwarding all method> calls to the internally stored PyCodeObject. That would work.
>&
On 7/11/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
At 10:56 AM 7/11/2006 -0700, Brett Cannon wrote:>On 7/10/06, Talin <[EMAIL PROTECTED]>[EMAIL PROTECTED]> wrote:>>(Although, I've often wished for Python to have a variant of __call__
>>that could be used
On 7/11/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Michael> Well here's one I stumbled across the other day. I don't knowMichael> if it's legit, but it's still bad PR:Michael>
http://www.gbch.net/gjb/blog/software/discuss/python-sucks.htmlMichael> For the impatient, he's not
On 7/11/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Brett> That whole entry is a little overblown.Well, sure. Think of it as a bug report with attitude. ;-)Brett> That was done to fix buffer overflow issues when libcBrett> implementations didn't do bound checks on the arguments to
On 7/12/06, Armin Rigo <[EMAIL PROTECTED]> wrote:
Hi Brett,On Tue, Jul 11, 2006 at 06:05:21PM -0700, Brett Cannon wrote:> It is the last point in the first paragraph on time.strftime() discussing> what changed in Python 2.4 as to what the change was. It's also in
> Misc/NEWS
On 7/12/06, Jim Jewett <[EMAIL PROTECTED]> wrote:
Ka-Ping Yee writes:> A. The interpreter will not crash no matter what Python code> it is given to execute.Why?We don't want it to crash the embedding app (which might be another
python interpreter), but if the sandboxed interpreter itself c
On 7/12/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
On 7/12/06, Armin Rigo <[EMAIL PROTECTED]> wrote:> I guess I'm going to side with Greg Black on his blog entry.I seem to recall that that particular one wass *not* an accidental
bug. I believe I fell over exactly the problem that Greg Blackcom
On 7/12/06, Anthony Baxter <[EMAIL PROTECTED]> wrote:
On Thursday 13 July 2006 14:46, Guido van Rossum wrote:> Thanks for confirming memory! So it was an intentional regression;> "bugs happen" doesn't apply in this case. And an unfortunate> regression at that -- not because one guy writes a silly
On 7/13/06, Greg Ewing <[EMAIL PROTECTED]> wrote:
Ka-Ping Yee wrote:> Having to 'import sys' to get at the command-line arguments always> seemed awkward to me. 'import sys' feels like it should be a> privileged operation (access to interpreter internals), and getting
> the command-line args isn't
On 7/13/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
On Thu, 13 Jul 2006 19:19:08 +0100, Michael Hudson <[EMAIL PROTECTED]> wrote:>[EMAIL PROTECTED] writes:>> For example, did anyone here know that the new-style exceptions stuff in
2.5>> caused hundreds of unit-test failures in Twisted? I am
On 7/14/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
Whoa, whoa. What's the *problem* we're trying to solve here?I have a use case for sandboxing. I am already having to plan to have a mini-sys module in a sandbox so that they cannot get access to dangerous things.
-BrettOn 7/14/06, Nick Coghla
On 7/14/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
On 7/14/06, Brett Cannon <[EMAIL PROTECTED]> wrote:> On 7/14/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:> > Whoa, whoa. What's the *problem* we're trying to solve here?
>> I have a use case for
On 7/17/06, matt westerburg <[EMAIL PROTECTED]> wrote:
Hi my name is Matt Westerburg, I am a student and have only recently gotten into Python. But have fallen in love with the language thus far. Fantastic language and thank you very much for making it what it is today. I am looking into getting
After various people suggesting object-capabilities, takling with Mark S. Miller of the E programming language, and the people Mark works with at HP Labs (who have been giving talks every week during this month here at Google on object-capabilities), I have decided to go with object-capabilities fo
On 7/20/06, Giovanni Bajo <[EMAIL PROTECTED]> wrote:
Brett Cannon wrote:>> The new doc is named securing_python.txt and>> can be>> found through the svn web interface at>>
http://svn.python.org/view/python/branches/bcannon-sandboxing/securing_python.txt?rev=50717&
On 7/20/06, Nick Coghlan <[EMAIL PROTECTED]> wrote:
For code objects, their construction is already commonly written as"compile(source)".Right, but some people like to construct directly from bytecode.
For type objects, the constructor doesn't let you do anything you can'talready do with a class s
On 7/20/06, Lawrence Oluyede <[EMAIL PROTECTED]> wrote:
That's great. I just read your draft but I have little comments to dobut before let me say that I liked the idea to borrow concepts from E.I've crossed the E's path in the beginning of this year and I found it
a pot of really nice ideas (for p
On 7/20/06, Giovanni Bajo <[EMAIL PROTECTED]> wrote:
Brett Cannon wrote:>>http://svn.python.org/view/python/branches/bcannon-sandboxing/securing_python.txt?rev=50717&view=log
>> .>>>> How do you plan to handle CPU-hogs? Stuff like execution of a>> gig
On 7/20/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
While investigating the need to apply http://python.org/sf/1525766 I foundthat there was a modification to pkgutil during the need-for-speed sprintthat affects the PEP 302 protocol in a backwards incompatible way.
Specifically, PEP 302 documents
On 7/20/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
At 12:28 PM 7/20/2006 -0700, Brett Cannon wrote:>On 7/20/06, Phillip J. Eby><[EMAIL PROTECTED]>[EMAIL PROTECTED]
> wrote:>>While investigating the need to apply>><http://python.org/sf/1525766>http://pyt
Here is a first stab at writing up guidelines for people to follow
when reporting bug. If this goes well I will also do ones for
patches, committing, and PEPs.
-Brett
---
These sets of guidelines are to help you file a bug report for the Python
p
On 7/20/06, Fred L. Drake, Jr. <[EMAIL PROTECTED]> wrote:
On Friday 21 July 2006 00:10, Neil Hodgson wrote: > Brett Cannon: > > But SourceForge does not support anonymous reporting. > >SourceForge does support anonymous reporting. A large proportion of
> the fau
On 7/22/06, Armin Rigo <[EMAIL PROTECTED]> wrote:> Re-hi,> > On Wed, Jul 19, 2006 at 03:35:45PM -0700, Brett Cannon wrote:> >
http://svn.python.org/view/python/branches/bcannon-sandboxing/securing_python.txt?rev=50717&view=log.> > I'm not sure I understan
On 7/22/06, Armin Rigo <[EMAIL PROTECTED]> wrote:
Hi Brett,On Wed, Jul 19, 2006 at 03:35:45PM -0700, Brett Cannon wrote:> I also plan to rewrite the import machinery in pure Python.
http://codespeak.net/svn/pypy/dist/pypy/module/__builtin__/importing.pyThanks for the link, Armin. Since
On 7/23/06, Armin Rigo <[EMAIL PROTECTED]> wrote:
Hi David, hi Brett,On Sun, Jul 23, 2006 at 02:18:48AM +0100, David Hopwood wrote:> If I understand correctly, the proposal is that any incompatible changes> to the language would apply only in "sandboxed" interpreters. So there is
> no reason why su
On 7/23/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
At 11:07 PM 7/23/2006 +0100, David Hopwood wrote:>Phillip J. Eby wrote:[snip]
Brett's securing_python.txt don't refer to or cite Zope in any way, butrather relies on broad and unsupported assertions about what can or can'tbe done with Python.
On 7/23/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
At 09:27 PM 7/23/2006 -0700, Brett Cannon wrote:When I say "name checker" I mean the Zope type that allows you to specify alist of names that are allowed for a given object. This allowing is not
based on identity or code sig
On 7/25/06, Neil Hodgson <[EMAIL PROTECTED]> wrote:
Martin v. Löwis:> Currently, we have two running tracker demos online: After playing with them for 30 minutes, Jira seems to have too busyan interface and finicky behaviour: not liking the back button
sometimes (similar to SF) and clicking on di
On 7/28/06, Charles Vaughn <[EMAIL PROTECTED]> wrote:
I'm looking for a way of modifying the compiler to eliminate any loops and recursion from code. It's for a high speed data processing application. The alternative is a custom language that is little more than gloryfied assembly. I'd like to b
On 7/31/06, Chad Whitacre <[EMAIL PROTECTED]> wrote:
Dear All,Last week I submitted a patch (my first),Thanks!
and now I'm wondering what myexpectations should be. Do I sit around and wait? How long? Do I notifythis list? Do I notify a specific person, say, an author or reviewer ofthe original co
On 7/31/06, Chad Whitacre <[EMAIL PROTECTED]> wrote:
Brett,Thanks for the helpful reply.> Let it sit for now. We get email notifications when new patches come in.Can I ask who "we" are? Is that the seven SF "Project Admins?" Is that
the 68 SF "Developers?""We" is most of the developers on python-d
My [EMAIL PROTECTED] SSH key should be removed since my internship is now over.-Brett
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/arch
On 8/5/06, Hernan M Foffani <[EMAIL PROTECTED]> wrote:
> > > > Currently, we have two running tracker demos online:> > > >> > > > Roundup:> > > > http://efod.se/python-tracker/
> > > >> > > > Jira:> > > > http://jira.python.atlassian.com/secure/Dashboard.jspa>>
> Is anyone looking at the Google Cod
e who took the time and effort to set up a test tracker to help improve the development of Python.- Brett Cannon Chairman, PSF Infrastructure Committee
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/pytho
On 8/20/06, Barry Warsaw <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-Hash: SHA1On Aug 20, 2006, at 11:24 AM, Guido van Rossum wrote:> I wonder if it would make sense to focus in 2.6 on making porting of> 2.6 code to 3.0 easier, rather than trying to introduce new features
> in 2.6.
On 8/22/06, Nick Coghlan <[EMAIL PROTECTED]> wrote:
brett.cannon wrote:> Added: peps/trunk/pep-0362.txt> +Relation With Other PEPs> +> +> +"Keyword-Only Arguments [#pep-3102]_> +
> +> +If keyword-only parameters come into existence, the Pa
On 8/22/06, Nick Coghlan <[EMAIL PROTECTED]> wrote:
brett.cannon wrote:> Added: peps/trunk/pep-0362.txt> +Relation With Other PEPs> +> +> +"Keyword-Only Arguments [#pep-3102]_> +
> +> +If keyword-only parameters come into existence, the Pa
On 8/23/06, K.S.Sreeram <[EMAIL PROTECTED]> wrote:
Hi all,I noticed in Python/ceval.c that LOAD_GLOBAL uses a dictionary lookup,and was wondering if that can be optimized to a simple array lookup.No, not as the language stands now.
If i'm right there are 3 kinds of name lookups: locals, outerscope
I have been spending my Google sprint time on writing and implementing PEP 362 (http://www.python.org/dev/peps/pep-0362/), which finally defines Signature objects for functions. With the implementation at a place I am happy with, I wanted to ask about the open issues with the PEP.
The first questi
On 8/23/06, Georg Brandl <[EMAIL PROTECTED]> wrote:
Brett Cannon wrote:> I have been spending my Google sprint time on writing and implementing> PEP 362 (http://www.python.org/dev/peps/pep-0362/), which finally
> defines Signature objects for functions. With the implementation a
Below is the current draft of a set of bug guidelines for people to follow when they want to file a bug. The hope is that when we get an email asking "how do I file a bug?" we can point them towards these sets of guidelines for most issues.
Let me know about any errors and such. This will (hopefu
Below is a draft for a set of patch guidelines. This is meant for that times where people ask "how do a create a patch for a change I made" or where to point people if they created a patch but it comes up short (no tests, etc.). Hopefully this will go up on
python.org/dev/ .Let me know of any er
Made it the first step. =)-BrettOn 8/24/06, Oleg Broytmann <[EMAIL PROTECTED]> wrote:
On Thu, Aug 24, 2006 at 12:21:06PM -0700, Brett Cannon wrote:> Start a new bug "Before starting a new bug please try to search if the bug has alreadybeen reported. It it has - do not start a n
On 8/24/06, Oleg Broytmann <[EMAIL PROTECTED]> wrote:
On Thu, Aug 24, 2006 at 12:22:42PM -0700, Brett Cannon wrote:> Read the Developer Intro to understand the scope of your proposed change "Search through the PEPs, developer mailing lists and patches. Has a
similar patch already
On 8/24/06, Chad Whitacre <[EMAIL PROTECTED]> wrote:
Brett, > Below is a draft for a set of patch guidelines.Thanks for getting around to this!Welcome.
> Wait for a developer to contact you > === > > At this point you need to wait for a Python developer to come alo
On 8/27/06, Chad Whitacre <[EMAIL PROTECTED]> wrote:
Brett, > When you submit your patch, the tracker notifies a mailing list that > most core Python developers subscribe to of the creation of your new > patch.Isn't "of the creation of your new patch" redundant? What else would it
be notifying the
On 8/28/06, Steve Holden <[EMAIL PROTECTED]> wrote:
Brett Cannon wrote:> Made it the first step. =)>> -Brett>> On 8/24/06, *Oleg Broytmann* <[EMAIL PROTECTED]>
[EMAIL PROTECTED]>> wrote:>> On Thu, Aug 24, 2006 at 12:21:06PM -0700, Brett Cannon wrote:&g
On 9/4/06, Neal Norwitz <[EMAIL PROTECTED]> wrote:
There are 3 bugs currently listed in PEP 356 as blocking:http://python.org/sf/1551432 - __unicode__ breaks on exception classesI replied on the bug report, but might as well comment here.
The problem with this bug is that BaseException now
On 9/5/06, Georg Brandl <[EMAIL PROTECTED]> wrote:
Brett Cannon wrote:>>> On 9/4/06, *Neal Norwitz* <[EMAIL PROTECTED]> [EMAIL PROTECTED]>> wrote:
>> There are 3 bugs currently listed in PEP 356 as blocking:> http://python.org/sf/1551432 -
1901 - 2000 of 3314 matches
Mail list logo
