On 9/5/06, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
Brett Cannon wrote:> 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&
On 9/7/06, Neal Norwitz <[EMAIL PROTECTED]> wrote:
On 9/5/06, Brett Cannon <[EMAIL PROTECTED]> wrote:>> > [MAL]> > The proper fix would be to introduce a tp_unicode slot and let> > this decide what to do, ie. call .__unicode__() methods on instances
> > and u
On 9/6/06, Ka-Ping Yee <[EMAIL PROTECTED]
> wrote:
Hi Brett,Here are some comments on your proposal. Sorry this took so long.I apologize if any of these comments are out of date (but also lookforward to your answers to some of the questions, as they'll help
me understand some more of the details o
On 9/7/06, Neal Norwitz <[EMAIL PROTECTED]> wrote:
On 9/5/06, Brett Cannon <[EMAIL PROTECTED]> wrote:>> > [MAL]> > The proper fix would be to introduce a tp_unicode slot and let> > this decide what to do, ie. call .__unicode__() methods on instances
> > and u
On 9/13/06, Sanghyeon Seo <[EMAIL PROTECTED]> wrote:
CPython 2.5, which will be released Real Soon Now, is the firstversion to ship with new "AST branch", which have been in developmentfor a long time.AST branch uses ASDL, Abstract Syntax Description Language
http://asdl.sourceforge.net/ to describ
On 9/16/06, Talin <[EMAIL PROTECTED]> wrote:
Lawrence Oluyede wrote:>> That was my first thought as well. Unfortunately a quick test shows>> that class Foo(): creates an old style class instead :(>> I think that's because until it'll be safe to break things we will
> stick with classic by defaul
On 9/18/06, Greg Ewing <[EMAIL PROTECTED]> wrote:
Armin Rigo wrote:> My (limited) understanding of the motivation for relative imports is> that they are only here as a transitional feature. Fully-absolute> imports are the official future.
Guido does seem to have a dislike for relative imports,but
On 9/20/06, Thomas Heller <[EMAIL PROTECTED]> wrote:
Is it an oversight that exception instances do no longer supportslicing in Python 2.5?This code works in 2.4, but no longer in 2.5:try:open("", "r")except IOError, details:
print details[:]Technically, yes. There is no entry in the sq_sl
On 9/20/06, Thomas Heller <[EMAIL PROTECTED]> wrote:
Brett Cannon schrieb:> On 9/20/06, Thomas Heller <[EMAIL PROTECTED]> wrote:>>>> Is it an oversight that exception instances do no longer support
>> slicing in Python 2.5?>>>> This code works in 2
On 9/21/06, Grzegorz Makarewicz <[EMAIL PROTECTED]> wrote:
Hi,- *.txt files for unicode tests are downloaded from internet - I don'tlike this.Then don't use the urlfetch resource when running regrtest.py (which you did specify when you ran with ``-uall``).
- __db.004 isn't removed after tests- init
luded a reimplementation of the built in import mechanism as> hooks. Is there any interest in this actually happening? I've been> looking for an interesting coding project for a while (although I
> never have any free time...)There's a general desire to reimplement import entirely in
On 9/22/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Michael> There are several different possible approaches in pure Python,Michael> but is this an idea that has legs ?Why not add it to itertools? Then, if you need a true list, just calllist() on the returned iterator.
Yeah, this is a
On 9/23/06, Anthony Baxter <[EMAIL PROTECTED]> wrote:
I'd like to propose that the AST format returned by passing PyCF_ONLY_AST tocompile() get the same guarantee in maintenance branches as the bytecodeformat - that is, unless it's absolutely necessary, we'll keep it the same.
Otherwise anyone tryi
I am at the point with my security work that I need to consider how I am going to restrict importing modules. My current plan is to basically implement phase 2 of PEP 302 and control imports through what importer objects are provided. This work should lead to a meta_path importer for built-ins an
On 9/27/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
At 02:11 PM 9/27/2006 -0700, Brett Cannon wrote:>But it has been suggested here that the import machinery be rewritten in>Python. Now I have never touched the import code since it has always had>the reputation of being less t
On 9/27/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
At 04:11 PM 9/27/2006 -0700, Brett Cannon wrote:>On 9/27/06, Phillip J. Eby><[EMAIL PROTECTED]>[EMAIL PROTECTED]
> wrote:>>At 02:11 PM 9/27/2006 -0700, Brett Cannon wrote:>> >But it has been suggested here th
On 9/27/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
At 05:26 PM 9/27/2006 -0700, Brett Cannon wrote:>Ah, OK. So for importing 'email', the zipimporter would call the .pyc>importer and it would ask the zipimporter, "can you get me email.pyc?" and
>if it said no
On 9/29/06, BJörn Lindqvist <[EMAIL PROTECTED]> wrote:
> If there are "rampant criticisms" of the Python docs, then those that> are complaining should take specific examples of their complaints to the> sourceforge bug tracker and submit documentation patches for the
> relevant sections. And person
I am working on PEP 352 stuff for 2.6 and there are two changes that I think should be made that are not explicitly laid out in the PEP.First, and most dramatic, involves what is legal to list in an 'except' clause. Right now you can listing *anything*. This means ``except 42`` is totally legal e
In the interest of time I have decided to go ahead and do the PEP 302 phase 2 work in C. I fully expect to tackle rewriting import in Python in my spare time after I finish this work since I will be much more familiar with how the whole import machinery works and it sounds like a fun challenge.
Th
On 10/2/06, Paul Moore <[EMAIL PROTECTED]> wrote:
On 10/2/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:[SNIP]> I'm surprised, however, that you think working on this in C is going to be> *less* time than it would take to simply replace __import__ with a Python
> function that reimplements PEP 302..
On behalf of the PSF Infrastructure committee, I am happy to report that we have reached a recommendation for a new issue tracker for Python!But first, I want to extend our thanks to all who stepped forward to provide the committee with a test installation of an issue tracker to use as a basis of o
On 10/3/06, Neal Norwitz <[EMAIL PROTECTED]> wrote:
On 10/2/06, Brett Cannon <[EMAIL PROTECTED]> wrote:>> This is why I asked for input from people on which would take less time.> Almost all the answers I got was that the the C code was delicate but that
> it was workab
The email didn't bounce; it was just held for moderator approval (and it made it through). Just sit tight and we will be getting back to all of the volunteers in the near future (probably next week, no later than after this upcoming week).
-BrettOn 10/6/06, Chuzo Okuda <[EMAIL PROTECTED]> wrote:
I
On 10/11/06, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
Martin v. Löwis wrote:> Of course, if everybody would always recompile all extension modules> for a new Python feature release, those flags weren't necessary.a dynamic registration approach would be even better, with a single entry point
used to
On 10/12/06, Anthony Baxter <[EMAIL PROTECTED]> wrote:
On Friday 13 October 2006 05:30, Georg Brandl wrote:> I'm I the only one who feels that the website is a big workflow problem?Assuming you meant "Am I", then I absolutely agree with you.
I have touched the web site since the Pyramid switch and
For the past couple years there has been the suggestion of having a panel discussion made up of core developers at PyCon. Basically it would provide a way for the community to find how we do things, where we are going, our views, etc.
I have finally decided to step forward and try to organize such
On 10/19/06, Paul Moore <[EMAIL PROTECTED]> wrote:
On 10/19/06, Anthony Baxter <[EMAIL PROTECTED]> wrote:> Anyway, all of the above is open to disagreement or other opinions - if you> have them, let me know.
My only thought is that you've done a fantastic job pushing throughall the recent releases.
On 10/19/06, Grig Gheorghiu <[EMAIL PROTECTED]
> wrote:
The latest trunk checkin caused almost all Pybots to fail when runningthe Python unit tests.273 tests OK.12 tests failed:test___all__ test_calendar test_capi test_datetime test_emailtest_email_renamed test_imaplib test_mailbox test_str
On 10/19/06, Grig Gheorghiu <[EMAIL PROTECTED]> wrote:
On 10/19/06, Brett Cannon <[EMAIL PROTECTED]> wrote:>> Possibly. If you look at the reason those tests failed it is because> time.strftime is missing for some odd reason. But none of recent checkins
> seem to have
On 10/19/06, Grig Gheorghiu <[EMAIL PROTECTED]> wrote:
On 10/19/06, Brett Cannon <[EMAIL PROTECTED]> wrote:>>> On 10/19/06, Grig Gheorghiu <[EMAIL PROTECTED]
> wrote:> > On 10/19/06, Brett Cannon <[EMAIL PROTECTED]> wrote:> > >> > > Poss
Forgot to send this to python-dev. =)-- Forwarded message --From: Brett Cannon <[EMAIL PROTECTED]
>Date: Oct 20, 2006 1:35 PMSubject: PSF Infrastructure has chosen Roundup as the issue tracker for Python developmentTo: python-list@python.orgAt the beginning of the month t
The initial admins for the Roundup installation have been chosen: Paul DuBois, Michael Twomey, Stefan Seefeld, and Erik Forsberg. The offer from Upfront Systems (http://www.upfrontsystems.co.za/
) has been accepted for professional Roundup hosting.Discussion of how to handle the new tracker (inclu
On 10/30/06, Travis E. Oliphant <[EMAIL PROTECTED]> wrote:> > Attached is my PEP for extending the buffer protocol to allow array data> to be shared.
You might want to reference this thread (http://mail.python.org/pipermail/python-3000/2006-August/003309.html) as Guido mentions that extending the b
On 11/1/06, Stefan Seefeld <[EMAIL PROTECTED]> wrote:
Brett Cannon wrote:> On 11/1/06, Stefan Seefeld <[EMAIL PROTECTED]> wrote:>> Right. Brett, do we need accounts on python.org
for this ?>>> Yep. It just requires SSH 2 keys from each of you. You can then email&g
On 11/1/06, Erik Forsberg <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-Hash: SHA1"Brett Cannon" <[EMAIL PROTECTED]> writes:> On 11/1/06, Stefan Seefeld <
[EMAIL PROTECTED]> wrote:>>>> Brett Cannon wrote:>> > On 11/1/06, Stefan Se
On 11/3/06, Robert <[EMAIL PROTECTED]> wrote:
repeated from c.l.p : "Feature Request: Py_NewInterpreter to createseparate GIL (branch)"Daniel Dittmar wrote: > robert wrote: >> I'd like to use multiple CPU cores for selected time consuming Python
>> computations (incl. numpy/scipy) in a frictionles
On 11/4/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
Fredrik Lundh schrieb:>> However, I find the proposed behaviour reasonable: Python already>> automatically imports the .pyc file if .py is not given and vice>> versa. So why not look for .pyo if the .pyc file is not present?
>> well, from a p
On 11/4/06, Osvaldo Santana <[EMAIL PROTECTED]> wrote:
Hi,I'm the author of this patch and we are already using it in Pythonport for Maemo platform.We are using .pyo modules mainly to remove docstrings from themodules. We've discussed about this patch here[1] before.
Now, I agree that the zipimport
On 11/4/06, Jean-Paul Calderone <[EMAIL PROTECTED]> wrote:
On Sun, 05 Nov 2006 14:21:34 +1300, Greg Ewing <[EMAIL PROTECTED]> wrote:>Fredrik Lundh wrote:>>> well, from a performance perspective, it would be nice if Python looked
>> for *fewer* things, not more things.>>Instead of searching for thin
On 11/5/06, Steve Holden <[EMAIL PROTECTED]> wrote:
[Off-list]Brett Cannon wrote:[...]>> Hopefully my import rewrite is flexible enough that people will be able> to plug in their own importer/loader for the filesystem so that they can> tune how things like this are handled (
On 11/6/06, Giovanni Bajo <[EMAIL PROTECTED]> wrote:
Martin v. Löwis wrote:>> Why not only import *.pyc files and no longer use *.pyo files. It is simpler to have one compiled python file extension.>> PYC files can contain optimized python byte code and normal byte
>> code.>> So what would you
On 11/15/06, Georg Brandl <[EMAIL PROTECTED]> wrote:
Hi,
this might seem a bit late, and perhaps I was just blind,
but I miss something like a summary how the Python
summer of code projects went, and what the status of the ones
that were meant to improve the standard library, e.g. the
C decimal
Discussion of what we want in terms of the schema for the new issue tracker
has begun. If you wish to give feedback on what you would like each issue
to have in terms of data then please file an issue in the meta tracker at
http://psf.upfronthosting.co.za/roundup/meta/ . You can see the current
On 12/4/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
Some people (Robert Schweikert) requested byte-code stability at the
LSB meeting: LSB should standardize a certain version of the byte code,
and then future versions of Python should continue to support this
byte code version.
Did they
On 12/4/06, Neil Toronto <[EMAIL PROTECTED]> wrote:
Martin v. Löwis wrote:
> Brett Cannon schrieb:
>
>> Did they say why they wanted to distribute bytecode files? I assume
it
>> is either for space considerations or they think it will help to
protect
>> th
On 12/5/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> "Martin" == Martin v Löwis <[EMAIL PROTECTED]> writes:
Martin> [EMAIL PROTECTED] schrieb:
>> >> All in all, I think providing binary compatibility would be
feasible,
>> >> and should be attempted. What do you think?
On 12/8/06, Anthony Roy <[EMAIL PROTECTED]> wrote:
Hi all,
I have a patch for the fileinput.FileInput class, adding a parameter
to the __init__ method called write_mode in order to specify the write
mode when using the class with the inplace parameter set to True.
Before I submit the patch, I'
On 12/12/06, Kay Schluehr <[EMAIL PROTECTED]> wrote:
Dear Python developers,
while the JVM is opened to support dynamically typed languages [1] I
wonder if the CPyVM could not show more openness to statically typed
languages? Hereby I don't think that much about arbitrary languages for
the CPyV
On 12/19/06, Andrea Griffini <[EMAIL PROTECTED]> wrote:
I'm experimenting with a patch for dictionary lookup caching, the
main idea being avoiding the lookup of a constant (co_names) in
a dictionary if the dictionary didn't change since last lookup.
Currently the cache is held in a structure th
At Guido's suggestion, a new mailing list has been created named
Python-Ideas (http://mail.python.org/mailman/listinfo/python-ideas). This
list is meant as a place for speculative, pie-in-the-sky language design
ideas to be discussed and honed to the point of practically being a PEP
before being
I just noticed that PEP 328 (relative imports) is listed as an accepted PEP,
but not completed. Is this because there is still things to do for 2.6 and
2.7? Or did someone just forget to move it to the completed PEPs section of
the PEP index? If it is the former then PEP 362 will need to be mov
On 12/20/06, Thomas Wouters <[EMAIL PROTECTED]> wrote:
On 12/20/06, Brett Cannon <[EMAIL PROTECTED]> wrote:
>
> I just noticed that PEP 328 (relative imports) is listed as an accepted
> PEP, but not completed. Is this because there is still things to do for
> 2.6
I originally posted this list to python-3000 since I figured we could
be more aggressive with Py3K, but Guido said I should move it over
here and just be aggressive in 2.6.
So, here are the platforms I figured we should drop:
* AtheOS
* BeOS
* FreeBSD 2 (maybe more?)
* IRIX
* NeXT
* OS/2
* UnixWa
On 12/22/06, A.M. Kuchling <[EMAIL PROTECTED]> wrote:
> http://www.python.org/sf/411881 is a bug about removing use
> of 'except:' in stdlib code. In many cases the intent is to catch
> one particular exception such as ImportError or AttributeError,
> but catching all exceptions can disguise othte
On 12/29/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
Brett Cannon schrieb:
> I originally posted this list to python-3000 since I figured we could
> be more aggressive with Py3K, but Guido said I should move it over
> here and just be aggressive in 2.6.
Please
On 1/2/07, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
On 2007-01-02 01:02, brett.cannon wrote:
> Author: brett.cannon
> Date: Tue Jan 2 01:02:41 2007
> New Revision: 53204
>
> Added:
>peps/trunk/pep-3108.txt (contents, props changed)
> Modified:
>peps/trunk/pep-.txt
> Log:
> Add PEP
On 1/2/07, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
On 2007-01-02 23:54, Brett Cannon wrote:
> On 1/2/07, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
>>
>> On 2007-01-02 01:02, brett.cannon wrote:
>> > Author: brett.cannon
>> > Date: Tue
On 1/2/07, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
On 2007-01-02 23:54, Brett Cannon wrote:
> On 1/2/07, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
>>
>> On 2007-01-02 01:02, brett.cannon wrote:
>> > Author: brett.cannon
>> > Date: Tue
On 1/3/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
Guido van Rossum schrieb:
> Maybe this should be done in a more systematic fashion? E.g. by giving
> all "internal" header files a "py_" prefix?
Yet another alternative would be to move all such header files into a
py/ directory, so you wo
On 1/4/07, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
On 2007-01-03 01:42, Brett Cannon wrote:
> On 1/2/07, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
>> >> > +Open Issues
>> >> > +===
>> >> > +
>> >> > +C
Finally, after a few months worth of work, I have finally gotten far enough
in my import rewrite that I am willing to stick my neck out and say it is
semantically complete! You can find it in the sandbox under import_in_py.
So, details of this implementation. I implemented PEP 302 importers/loa
On 1/9/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 1/9/07, Brett Cannon <[EMAIL PROTECTED]> wrote:
> > Should we bother with deprecating 'sets' in the 2.x series?
>
> I'd say so, yes.
>
OK, I work on
On 1/10/07, Georg Brandl <[EMAIL PROTECTED]> wrote:
> Hi,
>
> is there any objection against making python-ideas available on gmane?
> Should I just suggest it myself, or has someone to do extra admin work
> on the mailing list side?
>
Just email me personally the email address to subscribe.
-Bre
On 1/12/07, A.M. Kuchling <[EMAIL PROTECTED]> wrote:
> Forwarded for discussion from http://www.python.org/sf/1633665.
>
> --amk
>
> [forwarded from http://bugs.debian.org/327060]
>
> Many types in Python are idempotent, so that int(1) works
> as expected, float(2.34)==2.34, ''.join('hello')=='hell
On 1/12/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> On 12:37 am, [EMAIL PROTECTED] wrote:
>
> >For security reasons I might be asking for file's constructor to be
> >removed from the type for Python source code at some point (it can be
> >relocated to an extension module if desired). By for
On 1/14/07, Laurent Gautier <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> This is a somehow an update to the thread on pydoc started by Ron.
>
> Since the last entry we took the bull by the horns (so to speak), and
> are seriously aiming at delivering something that can qualify as:
> - a revision of the
tside of my Ph.D. thesis and thus I won't
be actively working on it (heck, this current work isn't either but I
have put so much time in at this point that my supervisor and I want
to get a published paper out of it eventually).
-Brett
> On 1/5/07, Brett Cannon <[EMAIL PROTECTED]&
I have discovered an issue relating to func_globals for functions and
the deallocation of the module it is contained within. Let's say you
store a reference to the function encodings.search_function from the
'encodings' module (this came up in C code, but I don't see why it
couldn't happen in Pyth
On 1/19/07, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
> On 2007-01-18 20:53, Brett Cannon wrote:
> > I have discovered an issue relating to func_globals for functions and
> > the deallocation of the module it is contained within. Let's say you
> > s
On 1/18/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Brett Cannon schrieb:
> > Anybody have any ideas on how to deal with this short of rewriting
> > some codecs stuff so that they don't depend on global state in the
> > module or just telling me
On 1/19/07, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
> On 2007-01-19 22:33, Brett Cannon wrote:
> >> That's a typical error situation you get in __del__ methods at
> >> the time the interpreter is shut down.
> >>
> >
> > Yeah, but in th
On 1/20/07, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
> On 2007-01-20 00:01, Brett Cannon wrote:
> > On 1/19/07, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
> >> On 2007-01-19 22:33, Brett Cannon wrote:
> >>>> That's a typical error situation
On 1/22/07, Michael Hudson <[EMAIL PROTECTED]> wrote:
> "Martin v. Löwis" <[EMAIL PROTECTED]> writes:
>
> > Bug #1579370 reports a crash when accessing the thread state of
> > a terminated thread, when releasing a generator object.
> >
> > In analysing the problem, I found that f_tstate doesn't hav
I am trying to commit to the 2.5 branch and I am getting an error:
svn: Commit failed (details follow):
svn: Can't create directory
'/data/repos/projects/db/transactions/53566-1.txn': Permission denied
Anyone know what is going on?
-Brett
___
Python-De
On 1/25/07, Tim Peters <[EMAIL PROTECTED]> wrote:
> [Brett Cannon]
> > I am trying to commit to the 2.5 branch and I am getting an error:
> >
> > svn: Commit failed (details follow):
> > svn: Can't create directory
> > '/data/repos/project
On 2/8/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> #1653736 reports that slot_nb_inplace_power has the wrong
> type: it should be a ternary function, but only is a binary.
> The proposed change is to make it ternary, and to invoke __ipow__
> with three arguments.
>
> In researching this, I c
On 2/9/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Brett Cannon schrieb:
> > Seems reasonable to me. Is the argument of None passed in
> > automatically somewhere?
>
> There are few callers of nb_inplace_power at all (AFAICT, only
> PyNumber_InPlaceP
On 2/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Guido> I'm not going to change ftplib.py and all the others.
>
> >> Also understood. This has, as far as I know, been the response of
> >> everybody who has encountered this problem before.
>
> Martin> You should read you
On 2/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Guido> I'm not going to change ftplib.py and all the others.
>
> >> Also understood. This has, as far as I know, been the response of
> >> everybody who has encountered this problem before.
>
> Martin> You should read you
On 2/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Mostly for my own curiosity, I'm working on a PEP-342-based
> microthreading library with a similar api to threads and threading
> (coalesced into a single module). It uses coroutines and a trampoline
> scheduler, and provides basic async
On 2/10/07, Steve Holden <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > On Sun, Feb 11, 2007 at 03:35:29AM +0200, Yotam Rubin wrote:
> >> Why don't you use Stackless? It's very simple, stable, and solves
> >> quite completely the problems in writing concurrect code.
> >
> > That's a grea
On 2/11/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Someone checked in Parser/Python.asdl. After rebuilding Subversion tells me
> that Python/Python-ast.c has been modified. I assume the two are related.
> Did whoever checked in the former need to check in the latter
Yeah, sorry about tha
On 2/11/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 2/11/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > Actually, the regenerating should happen immediately after commit,
> > as this bumps the revision number of the asdl file. This means
> > you have to make two commits per AST gramm
On 2/11/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Brett Cannon schrieb:
> > On 2/11/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >> Someone checked in Parser/Python.asdl. After rebuilding Subversion tells
> >> me
> >> tha
On 2/11/07, Ben North <[EMAIL PROTECTED]> wrote:
[SNIP]
> * The draft currently allows a two-argument form, to supply a default
> value if the object has no attribute of that name. This mimics the
> behaviour of the three-argument form of getattr, but looks a bit wrong:
>
> s = obj.(attr_
On 2/12/07, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
> [Jack Jansen]
> > I like the functionality, but I don't like the syntax, to me it looks
> > too much like a method call.
> >
> > To me self.[method_name] = self.metadata.[method_name] looks better:
> > what we're doing here is more like dic
On 2/12/07, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
> [Raymond Hettinger]
> >> Rather than munge existing syntaxes, an altogether new one would be
> >> more clear:
> >>
> >>self->name = self.metadata->name
>
> [Ben North]
> > One thing which comes to mind about this one is that, for C/C++
On 2/12/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> FWIW, I'm strongly -1 on the "->" notation. As a C programmer it's got
> too many neurons committed to it.
>
> I recommend that you do some experiments with the readability of the
> .[...] notation, e.g. write a program that randomly generat
On 2/12/07, Collin Winter <[EMAIL PROTECTED]> wrote:
> I've been working this past week at converting the stdlib's compiler
> package to use 2.5's new _ast module instead of the package's own AST.
> Overall, _ast was a joy to work with, save for the following nitpicks:
>
> 1) There are times when t
On 2/13/07, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Taking a step back a bit... the basic issue is that we have an attribute
> namespace (compile time key determination) that we want to access in a
> dictionary style (runtime key determination).
>
> This is currently done by switching from syntac
On 2/13/07, Greg Ewing <[EMAIL PROTECTED]> wrote:
> Brett Cannon wrote:
> > On 2/12/07, Collin Winter <[EMAIL PROTECTED]> wrote:
> > > 2) {BinOp,AugAssign,BoolOp,etc}.op
> >
> > I can't think of a reason, off the top of my head, why they can
On 2/16/07, Derek Shockey <[EMAIL PROTECTED]> wrote:
> Though I am an avid Python programmer, I've never forayed into the area of
> developing Python itself, so I'm not exactly sure how all this works.
>
> I was confused (and somewhat disturbed) to discover recently that the
> zipfile module offers
On 2/14/07, Sokolov Yura <[EMAIL PROTECTED]> wrote:
> It could be interesting.
>
> """
> - pyvm is * 2 times * faster than Python 2.4. In the source code there
> is a collection of benchmarks which includes 65 python scripts collected
> from the internet. At average if Python 2.4 needs 24 hours t
On 2/16/07, Collin Winter <[EMAIL PROTECTED]> wrote:
> On 2/14/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > Collin Winter schrieb:
> > > What's inconsistent about it? That classes are being used for the
> > > _ast.{Add,Sub,Mult,etc} names?
> >
> > Exactly. These aren't names - they are node
As Steve said, this is the wrong place to be asking for help about
this. We have *nothing* to do with mailing lists or Mailman.
Please read Steve's email again and follow the link in it. The people
on this list cannot help you with what you are asking for.
-Brett
On 2/21/07, Juan Carlos Suarez
On 2/22/07, Gabriel Becedillas <[EMAIL PROTECTED]> wrote:
> I'd hit an access violation inside PyErr_WriteUnraisable when a
> non-exception instance was raised. The call to PyExceptionClass_Name
> with a non-exception instance is yielding an invalid pointer.
> We are embedding Python 2.5 and a stri
When I gave the PSF members an update on the work to move the
python-dev tracker over to Roundup Andrew Kuchling asked me to also
send an email to python-dev since October/November.
As of right now the biggest thing holding up the transition is
documentation. A doc needs to get written explaining
Thanks! Hopefully someone will be able to get to it in the near future.
-Brett
On 2/26/07, Gabriel Becedillas <[EMAIL PROTECTED]> wrote:
> Brett Cannon wrote:
> > On 2/22/07, Gabriel Becedillas <[EMAIL PROTECTED]> wrote:
> >> I'd hit an access violation
On 3/2/07, Jim Jewett <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
>
> > Since this can conceivably be going on in parallel in multiple
> > threads, we really don't ever want to be sharing whatever object
> > contains the head of the chain of tracebacks since it mutates at every
> > frame b
2001 - 2100 of 3314 matches
Mail list logo
