_attrview(self):
> return self.__dict__
> attr = property(_attrview)
That wouldn't work: you really need to invoke the entire attribute
lookup machinery (e.g. to find methods, invoke properties, and so
on). Also, for 2.6, it wouldn't support old-
Mike Klaas schrieb:
> The entire codebase was developed post-2.4
Can you find out what percentage of these could have used
a __getitem__ if it had been implemented? As a starting
point, count all 'getattr(self' invocations.
Regards,
Martin
_
ause a performance
loss, not a performance gain, because of the additional
tests.
If you want to sure, you need to make some measurements
(e.g: what is the percentage of EQ and NE invocations,
in how many cases are both strings interned, and in
what percentage of these cases
e interned strings?
Because it's generated code. It has to follow rules, and it would
be good if there were few exceptions.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubs
e line numbers for every
token in the AST), but I can't see anything wrong with it, either
(except for the change in the structure, of course, but that will
happen, anyway).
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
return NULL; /* cannot happen */
}
Not sure what interned strings have to do with it.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python
#x27;)
I think this would violate the policy that a mutating function shouldn't
give the object being modified as the result - just as list.reverse
doesn't return the list, in addition to reversing it in-place.
Regards,
Martin
___
Python-Dev mai
,
> after all) or adding a new hook for the three-argument pow().
It's in the way in the sense that slot_nb_inplace_power discards its
third argument silently. That shouldn't happen, so I still prefer
removing it throughout. Would you volunteer adding to fix that?
Regards,
Martin
_
at are equal are guaranteed to be identical. So
if strings are not identical and both interned, it could infer that
they can't be equal, but currently doesn't infer so (instead, it
compares length and contents in this case).
Regards,
Martin
___
equally brief and to-the-point.
Would you like to do the same for Pass, Break, Continue, and Ellipsis?
They are also "just names". If you make _ast.Add the entry in the
tree itself, why not _ast.Break? Or, if you have a way to deal with
_ast.Break, why can't the same way work for
me-out value to trade business vs. responsiveness).
The 'run one iteration' approach doesn't support writing applications
that are single-threaded, responsive, and idle when there is nothing
to do. I can't believe that coroutines help in any way here.
Regards,
Martin
__
The-Main-Event-Loop.html
Regards,
Martin
___
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/archive%40mail-archive.com
# processor do "more than one thing at a time".
and goes on suggesting that asyncore provides one of them.
Regards,
Martin
___
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/archive%40mail-archive.com
tion doesn't need to be
> written thread-safe, PerfectReactor is platform-agnostic, and you don't
> have to know in advance all the event types you might ever listen to.
>
> Sorry if this is a dumb question (or if I'm mangling
eter
must occur in this thread, including the reactor calls.
So if the PerfectReactor is to support Tcl/Tk, it needs to run
the Tcl even loop in the Tcl thread, which is normally the
main thread (in Tkinter, it's the thread where you originally
created the tkapp object). OTOH, PerfectReactor may
e indexed access is deprecated, and only preserved for backwards
compatibility. So why would a new type be handy for os.stat?
And, if it's not for os.stat, what other uses does it have?
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python
nd copying) every time you needed to
> pass it to something that used indexed access.
Can you give a few example, for libraries where this isn't already done?
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python
cessarily be rewriting: In the C API, you have already
the PyStructSequence machinery (see posixmodule.c:stat_result_fields
for an example). It's just that this machinery isn't available to
Python code, yet, and no alternative convenience library is, either
(other than using __slots__, whi
nd I believe CP4E has
> been dropped from the agenda.
Ah, this passive voice again, and again the assumption that there is an
agenda of python-dev.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/list
,
it's a means of transition and backwards compatibility. For your
code, it seems you want it a permanent feature in your code.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsub
handling is as robust as it needs to be for the stdlib. I'd
> appreciate any insight into the issue or direction on where I might
> proceed from here so as to fix what I see as a significant problem.
I think something like this is patch #1121142.
Regards,
Martin
_
ot;.
I like this better. The base class you are looking for is _ast.operator;
it should be already there (please do take a look at Python.asdl to
see how I came to this conclusion, without studying the _ast module
again).
Regards,
Martin
___
Python-Dev mailing lis
to implement a patch to eliminate unnecessary
system calls, please submit it to sf.net/projects/python.
Regards,
Martin
___
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/archive%40mail-archive.com
ently named 'closure' (it's called
closure in many places already, and 'unused' in others).
I would also apply this part of the change, and both to
the trunk and Python 2.5. Objections?
Regards,
Martin
___
Python-Dev mailing list
gs
before people would start complaining that Python is unstable on
64-bit systems. By the time people would actually see problems,
hopefully they all have been resolved.
Regards,
Martin
___
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/archive%40mail-archive.com
xpect that you "normally"
cannot exercise the "large collections" feature of Python 2.5
on such an installation, because you have not enough memory
(in particular if the system was built in 1995).
Regards,
Martin
___
Python-Dev mailing list
f somebody answers "yes" to your
question?
Regards,
Martin
___
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/archive%40mail-archive.com
tinue to inherit from the integer type.
One idiom that people use a lot is foo[b], where
b is a boolean.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.p
e *same* Python version,
since it requires libraries not available in this other installation.
So the default must stay as it is.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubsc
at the
patch is unnecessary, i.e. it fixes a problem which shouldn't
arise in the first place.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.pytho
Greg Ewing schrieb:
>> One idiom that people use a lot is foo[b], where
>> b is a boolean.
>
> Could that be addressed using the new __index__ mechanism?
That would be possible, yes.
Martin
___
Python-Dev mailing list
Python-D
> in 2.5 as well (as long as arguments previously ignored don't suddenly
> raise exceptions, but it doesn't sound like that's happening at all.)
That change does not change behaviour at all.
Regards,
Martin
___
Python-Dev mailing l
te to the project anymore, but there are
many committers who have "silently" withdrawn, and that's really no
problem, either.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-d
de) still remains at the moment. It may be
sensible to remove it when Python 3 has solved the issue in some
other way, but then, removing it may cause unnecessary breakage, so
it can just as well stay throughout 2.x.
Regards,
Martin
___
Python-Dev mailing list
P
he style-guide in C is that macro names are spelled in all-caps, so
if you see an all-caps identifier, you expect it to be a macro name.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-d
t I was curious if any thought had been given
> to the future of the 2.x series.
You are mistaken. The 64-bit versions (AMD64 and Itanium) are not
compiled using MSVC 2003 - this product does not even include
compilers for this platform. Instead, they are compiled with the
SDK compil
in, what 2003 compiler did you recompile with? There is none.
Regards,
Martin
___
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/archive%40mail-archive.com
e the AST
>objects involved with the Grammar change.
This will also change when asdl_c.py runs.
> __ Parser/pgen needs to be rerun to regenerate Include/graminit.h
>and Include/graminit.c
This will also be done by the makefile automatically
and when, and who added the
documentation, and when. I often do that to verify that I really
understood the purpose of the question.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscri
o convert PCBuild/pcbuild.sln works
> okay. Am I missing something?
Yes, it doesn't work in Python 2.5 as released. This specific problem
has been fixed in the trunk and the 2.5 branch several months ago,
so I recommend to use either of these (or use VS 2003 to build the
releas
ectory should be used when building in 64
> bit on Win64.
No. The official binaries both for Itanium and AMD64 (which are both
"in 64 bit on Win64") are created with the PCbuild directory. See
PCbuild/readme.txt.
Regards,
Martin
___
Pyth
ted that?
Implementation-wise, I would expect that long_format already does the
bulk of what you need to do.
OTOH, also look at _PyString_FormatLong.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listin
, and run whatever conversion scripts are necessary.
In this case, the task would be merely to communicate that people
can already do that if they want to.
Regards
Martin
P.S. I'm really pissed as being described as member of a mafia.
___
Python-Dev maili
is mentoring potential future core developers.
So what do you do with core developers that don't do their job? Fire them?
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscrib
her changes. About the
only private mail that I exchange is about the mechanics of the
release process (e.g. agreeing on specific days for a release).
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/lis
heir way right at the start is completely
> counter-productive.
And please be assured that no such obstacle is in the submitters way.
Most patches are accepted without the submitter actually reviewing any
other patches.
Regards,
Martin
___
Python-Dev
formally complete before being
submitted. This is an area were anybody can review: you don't need
to be an expert to see that no test cases are contributed to a
certain patch.
If you really want to learn and help, review a few patches, to see
what kinds of pro
's it? Won't you need to publish the repository somehow?
Apache configuration? init.d scripts?
Regards,
Martin
___
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/archive%40mail-archive.com
to python-dev about your findings (proposals of acceptance
or rejection).
Regards,
Martin
___
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/archive%40mail-archive.com
tually did look
at the patch. If none of the committers have the time to do so, somebody
else must send the manual confirmation.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubsc
n't have anything better to do".
Shortly afterwards, he was a committer.
Regards,
Martin
___
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/archive%40mail-archive.com
group of core developers. It can't be
> any other way, it seems to me.
It might be that individuals get designated maintainers: Guido maintains
list and tuple, Tim maintaines dict, Raymond maintains set, I maintain
configure.in. However, I doubt that would work in practice.
Regards,
Martin
is is free software, it has its own working principles that people
need to get used to. In essence: if you want change, you need to execute
it your own. Nobody will do it for you.
Regards,
Martin
___
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/archive%40mail-archive.com
ee how to do that in a productive and rewarding way.
Not sure how long you have been contributing to free software: you will
find, over time, that it is rewarding to get changes accepted even if
the process takes several months. Patience is an important quality here.
Regards,
Martin
___
additional changes they like to see.
>
> Do you think this actually happens in practice?
I wasn't talking in general, I was talking specifically about you
(Phil Thompson) here. If you really want to contribute in
*maintaining* Python, you are more than welcome. Several current
ime person should be taken seriously.
That's quite expensive, plus somebody would need to supervise that
person. A part-time person would be less expensive, but still needs
supervision.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.
I hope Scott can clarify that), I can't find anything.
Assuming Scott's SF account is "geekmug", I don't see any open patches
(1574068 was closed within 20 days by amk, last October).
Regards,
Martin
___
Python-Dev mailing list
be changed? Opinions?
Regards,
Martin
___
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/archive%40mail-archive.com
honrc is the extension.
Regards,
Martin
___
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/archive%40mail-archive.com
patches reviewed...).
Regards,
Martin
___
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/archive%40mail-archive.com
Oleg Broytmann schrieb:
> On Tue, Mar 06, 2007 at 04:00:01PM +0100, "Martin v. L?wis" wrote:
>>>Yes. In .pythonrc.py .pythonrc is the root, and .py is the extension.
>> Ah, it would do that already: with multiple dots, the last one always
>> provides the exte
needs to produce a certain log message...
Regards,
Martin
___
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/archive%40mail-archive.com
cess, I think
it so happened that committers always found a mentor. It so happened
that some developer activated privileges for them (either himself, or
requesting that this be done), and then certainly feels responsible
for his 'student'. This automatically
in all
these years, nobody else commented that the patch was incomplete,
let alone commenting on whether the feature was desirable.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
;%' string
> formatting in my code with it.
That is fine. However, don't trade efficiency for maintainability.
Keep encapsulation of types, this is what OO is for. Modularize
along with type boundaries. If that loses efficiency, come up with
interfaces that still modularize in that
Oleg Broytmann schrieb:
>>>> os.path.splitext(".pythonrc")
> ('', '.pythonrc')
>
>and I think it should be
>
> ('.pythonrc', '')
Thanks, so it sounds like the patch should be accepted.
Regards,
Martin
_
e
is fine, but lacks a test case.
Regards,
Martin
___
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/archive%40mail-archive.com
is
"about right". People familiar with these tools probably learn
to do initial checkouts over night.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://ma
trigger, and the default behavior will be the correct one.
Regards,
Martin
___
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/archive%40mail-archive.com
ejected it because they thought
it was meant to do something else (namely, to do what it actually
did).
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/
'm just getting a hang when I execute:
>
> svn checkout svn+ssh://[EMAIL PROTECTED]/python/trunk
>
> I've only let it go for about 5 minutes so far, so maybe it's thinking
> about something, but I suspect it isn't...
>
> Anyone have any idea what I've
ion.
I also fail to see why it is useful to invoke splitext on a file name
to find out whether it is .svn - I would rather check the file name
itself.
It's unfortunate, of course, that people apparently relied on
this behavior (is the code you are referring to publicly available?
If so, where
ociated with a Python executable.
Yes (although I'm not sure what a "library binary" is).
Regards,
Martin
___
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/archive%40mail-archive.com
ld need to
be taken), feel free to post to python-dev (ideally with a
python.org/sf/number link so people can easily follow your
analysis), with a subject like "recommend for
rejection/acceptance".
The tricky ones are really the incomplete ones: if neither
the submitter nor you yourself
Larry Hastings schrieb:
> Hope this helps,
Indeed it does! After all this discussion, a documentation clarification
is certainly in order, but I can work that out myself.
Thanks,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
h
h the roundup maintainers to add that (although it
will likely only happen after the switch to roundup - it is
easy to extend the schema with additional fields if it is
known exactly what they are).
There is also a generic "keywords" field in the roundup
tracker - perhaps t
David Abrahams schrieb:
> on Tue Mar 06 2007, "Martin v. Löwis" wrote:
>> David Abrahams schrieb:
>>> I'm trying to find the Python library binaries associated with a given
>>> python executable.
>> This really isn't a python-dev quest
Phillip J. Eby schrieb:
> At 10:01 PM 3/6/2007 +0100, Martin v. Löwis wrote:
>> It's unfortunate, of course, that people apparently relied on
>> this behavior
>
> I was going to say it's the *documented* behavior, but I see that the
> documentation is actually
ific
> Looking at some code that works most of the time because the authors
> tried to deduce intention by looking at the Python source and existing
> installations isn't much better than trying to deduce intention by
> looking at the Python source and existing installations m
e case of splitext shows: you were in
>> favor of rejecting it because of the incompatibility, ...
>
> (I think that was actually John J. Lee; I did just add a note that it
> should no longer be considered bugfix candidate for 2.4)
Oops, sorry, confusing different JJs here (this m
ned to someone else, but at least it initially gives
> all issues to the person nominally responsible for it.
The SF tracker has this also. I'm auto-assigned for Tkinter bugs, for
example - not that I review them in a timely manner.
Regards,
Martin
___
nge existing semantics,
> though. For example, a "guess_mime_type(path)" function which could
> examine a path and figure out its mime type based on its extension
> (among other things).
I disagree. The current behavior is incorrect (and always has been);
the new behavior i
ontain incompatible
behavior. Just look at the "porting to" sections of past whatsnew files.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailma
tion.
Well, the tracker does have a status for each individual report: open or
closed. open means "needs more work", closed means "no more work
needed". So don't wade through a report - just assume that if it is
open, it needs work.
Regards,
Martin
), .readline(),
> etc); support for BZIP2 compression; support for removing a member
> file; support for encrypting/decrypting member files.
Unfortunately (?), the 2.6 zipfile module will have much of that, also,
please take a look.
Regards,
Martin
___
Giovanni Bajo schrieb:
> On 06/03/2007 10.52, Martin v. Löwis wrote:
>
>> I can't see that the barrier at contributing is high.
>
> I think this says it all. It now appears obvious to me that people
> inside the "mafia" don't even realize there is one.
out relative
> --prefix
> 1339673 - superseeded by #1597850
Thanks. Comming back to it only now, I added them into
http://wiki.python.org/moin/PatchTriage
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/l
's patch that it be closed in favour of
> yours.
This also sounds good.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/option
ly, offer a flag argument in splitext to differentiate
> between the two cases.
This isn't compatible, either, as older versions will raise an exception
because of the extra argument.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@py
[the chancellor]
> brought with him to Bonn.
> """
>
> (Martin, I certainly didn't intend to offend anyone by implying that
> they were part of a criminal organization. ;)
Apology accepted. As to your specific comments:
> there's definitely a group of "tru
You don't have to know. As a general contributor, just submit your
patch, and perhaps the reviewer will catch the error. As a submitter,
just submit the code, and George Yoshida will catch it. It's not
strictly necessary that the documentation actually builds all
the time. If you want to
I don't use IRC (or any other chat infrastructure),
as a matter of principle. The only way to talk to me "in real time" is
in person, or on the phone. (I do make an exception for the PSF board).
Regards,
Martin
___
Python-Dev mailing list
Py
y.
It's not a general approach. It's a case-by-case decision. Please
understand that *any* change is "incompatible", in the sense that
I can come up with an application that breaks under the change.
Really. *ANY CHANGE*. So the only way to get 100% compatibility
is to not chang
itial form; for many
of them, the biggest problem is that they lack documentation.
There was a phase when patches got accepted with no documentation,
for these modules, it was very difficult to come up with documentation
in the following years.
Regards,
Martin
_
for the old functionality. I really don't
see it (pje claimed he needed it once, but I remain unconvinced, not
having seen an actual fragment where the old behavior is helpful).
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
htt
18.17.1. However, looking at the tex, I cannot
find anything suspicious. texcheck complains about a missing ),
which I added, but it only was a problem of the text, not of the
markup.
Some tex guru will have to figure this out; please submit a
bugreport (if you can't figure it out yours
y found that people apparently do
back_name = splitext(name[0]) + '.bak'
which would severely break if somebody tried to create backups of
dotfiles that way.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mai
. When people actually care, they can easily
achieve compatibility across versions.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/opti
about object.h for Python 2.6.
Regards,
Martin
___
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/archive%40mail-archive.com
the PEP, and I understand "incompatible
change" as "programs only relying on document behavior might break".
In the case that triggered the discussion, the change implemented
was not an incompatible change, because the new implementation still
met the old specification
2401 - 2500 of 5755 matches
Mail list logo
