On 3/19/2010 2:23 AM, Laurent Gautier wrote:
On 3/19/10 3:36 AM, C. Titus Brown wrote:
Hi all,
once again, the PSF has been accepted as a mentoring foundation for
the Google
Summer of Code! This year, we're going to emphasize python 3 porting, so
please think of projects you'd like to see tackl
On 3/19/2010 10:22 AM, R. David Murray wrote:
This can be done by anyone just by saying, eg: 'see issue 1234' (roundup
turns that into a link),
That should be 'see issue #1234' to get the autolink.
From http://wiki.python.org/moin/TrackerDocs/
The tracker converts some specially formatted wor
On 3/19/2010 5:00 AM, Dirkjan Ochtman wrote:
On Thu, Mar 18, 2010 at 22:38, Terry Reedy wrote:
Having gotten that far, I think this might be worth referencing in new dev
docs.
Will do. I finally read hginit yesterday, after having seen people
rave about it on twitter for a few weeks, and
On 3/19/2010 8:46 AM, Alex A. Naanou wrote:
A friend of mine stumbled upon the following behavior:
[snip]
Questions like this are more appropriately posted to python-list, where
you would have gotten the same answer.
tjr
___
Python-Dev mailing li
On 3/19/2010 2:11 PM, Antoine Pitrou wrote:
Raymond Hettinger gmail.com> writes:
The reason to prefer an exception is that decimal/float comparisons
are more likely to be a programmer error than an intended behavior.
If you really believe that, then equality comparisons should also be
disa
On 3/19/2010 3:16 PM, Glenn Linderman wrote:
I perceive that the whole thread is about _all_ comparison operators with
one float and one decimal operand currently producing an exception (3.x)
Not true for equality comparison. That returns False regardless of
value, just as order comparisons r
On 3/20/2010 7:06 AM, Mark Dickinson wrote:
Will this change the result of hashing a long? I know that both gmpy
and SAGE use their own hash implementations for performance reasons. I
understand that CPython's hash function is an implementation detail,
but there are external modules that rely on
I did not receive the usual Friday tracker post on issues opened and
closed during the past week.
Did anyone else?
I am reading via gmane.
Terry Jan Reedy
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python
On 3/21/2010 1:12 PM, Benjamin Peterson wrote:
On behalf of the Python development team, I'm joyful to announce the second
bugfix release of the Python 3.1 series, Python 3.1.2.
Thanks for the work.
This bug fix release fixes numerous issues found in 3.1.1, and is considered a
production rele
On 3/22/2010 2:15 PM, Antoine Pitrou wrote:
What I am proposing is that the creation of __pycache__ /directories/ be put
outside of the core. It can be part of distutils, or of a separate module, or
delegated to third-party tools. It could even be as simple as
"python -m compileall --pycache", i
On 4/1/2010 7:20 PM, Andrew Svetlov wrote:
using of copy.copy for simple iterators is forbidden
import copy
copy.copy(iter([1, 2, 3]))
Traceback (most recent call last):
File "", line 1, in
File "/home/andrew/projects/py3k/Lib/copy.py", line 96, in copy
return _reconstruct(x, rv, 0)
On 4/5/2010 10:54 AM, will...@ufpa.br wrote:
for a college project, I proposed to create a compiler for python. I've
read something about it and maybe I saw that made a bad choice. I hear
everyone's opinion respond.
If you want to do something useful, pick an existing project (several
have alr
I may be missing the point, but ISTM that the assumption of this
approach is that there are often collisions in the hash table. I think
that assumption is false; at least, I recommend to validate that
assumption before proceeding.
It's just an experiment for a class, not something I am (yet)
s
On 4/10/2010 2:53 PM, Denis Kolodin wrote:
The first thing I want to say about is an extension of CSV api.
I believe speculative proposals like this fit better on the python-list
or python-ideas list.
tjr
___
Python-Dev mailing list
Python-Dev@py
On 4/11/2010 6:43 AM, Greg Ewing wrote:
import sys
try:
raise ValueError
except ValueError:
tb = sys.exc_info()[2]
print tb
print tb.__class__
# 3.1.2
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/lis
On 4/13/2010 10:17 AM, Anand Balachandran Pillai wrote:
>>I am surprised to see that the bug-tracker
>> doesn't have an OS classifier or ability to add
>> tags ? Since a number of issues reported seem to
>
> There is one. In the Components you can do a multip
On 4/15/2010 11:01 PM, Guido van Rossum wrote:
pyc files inside of the `__pycache__` directories contain a magic
identifier in their file names. These are mnemonic tags for the
actual magic numbers used by the importer. For example, in Python
3.2, we could use the hexlified [10]_ magic number a
On 4/16/2010 11:22 AM, Dino Viehland wrote:
Mark Dickinson wrote:
Removing it certainly seems in keeping with the goal of making life
easier for alternate implementations. (Out of curiosity, does anyone
know what IronPython does here?)
I've opened http://bugs.python.org/issue8419
It looks l
On 4/25/2010 4:31 PM, Sean Reifschneider wrote:
I'm trying to get a good friend of mine to start doing bug triage on Python.
What is *his* interest? How long has he known and used Python?
As part of my trying to mentor him on it, I've found that many of the common
things I do in triage, like
On 4/26/2010 11:09 AM, Alexander Belopolsky wrote:
I also I don't remember ever seeing spam in the bugs.python.org
comments which suggests that the subscription process weeds bots
reasonably well.
And when it fails, spam is deleted just so no one does see it.
_
On 4/26/2010 7:45 AM, Michael Foord wrote:
So the question remains - for *tracker* privileges, should the
recommendation and commitment to mentor from an established commiter be
sufficient (and therefore a standard part of our process)?
I think this is a reasonable barrier for entry and should
On 4/26/2010 2:12 AM, Sean Reifschneider wrote:
On Sun, Apr 25, 2010 at 08:42:00PM -0400, Terry Reedy wrote:
What is *his* interest? How long has he known and used Python?
Good points have been made on both sides of the issue here. Despite my
having a vested interest, I really have no strong
Currently, the 'default' Priority for new tracker issues is '- no
selection -'. This is, I believe, widely understood to be equivalent to
'normal'. Consequently, almost no one bothers to make a selection. This
applies even to experienced people like (in the last hour) Jesus Crea
(#8536), Eric S
On 4/26/2010 2:15 PM, Steve Holden wrote:
If this were the criterion then the answer would be simple: nobody seems to
knows dangerjim in the Python community.
Except, of course, the person recommending him. And it seems from the
discussion that nobody is particularly bothered about finding out
On 4/26/2010 3:22 PM, Steven D'Aprano wrote:
That depends on what you call unglamourous work. No, I don't triage
bugs. I don't have commit privileges, so I can't.
Tracker 'privileges' (responsibilities, really) are different from
commit privileses.
> Does hand-holding
newbies who don't know
On 4/26/2010 4:41 PM, Eric Smith wrote:
Martin v. Löwis wrote:
If possible, I think 'normal' should be the default in the hox or else
there should be some sort of auto replacement.
Makes sense to me.
I have now changed to make 'normal' the default priority for new issues.
Just now, I still
On 4/26/2010 5:02 PM, "Martin v. Löwis" wrote:
Eric Smith wrote:
Martin v. Löwis wrote:
If possible, I think 'normal' should be the default in the hox or else
there should be some sort of auto replacement.
Makes sense to me.
I have now changed to make 'normal' the default priority for new is
On 4/27/2010 4:38 PM, "Martin v. Löwis" wrote:
Done!
When I open http://bugs.python.org/iss...@template=item
priority is (still) set at no selection. Is this my local cache (which I
do not know how to clear in FF) or is 'normal' filled in after submission?
I do verify that searching for any
On 4/27/2010 5:14 PM, "Martin v. Löwis" wrote:
The page doesn't document the Resolution or Status fields.
The resolutions are the same as the ones on SourceForge.
They no longer have to be (see below). In any case, the meanings should
be independently documented here for people not currently
On 4/29/2010 1:58 PM, Bill Jordan wrote:
I am sorry if this is not the right list to post some questions.
You cross-posted to 4. Not good as answers will go to all 4 if
responders are not careful. Gmane.comp.python.devel is only for the
development of the next versions of CPython and mainly f
On 5/6/2010 9:50 PM, A.M. Kuchling wrote:
FYI: I've just added the text below to the "What's New" document for
2.7. I wanted to describe how 2.7 will probably be maintained, but
didn't want to write anything that sounded like an iron-clad guarantee
of a maintenance timespan. Does this text seem
There is obviously interest in your proposal. I suggest you open an
issue on the tracker. Make it a library feature request for 3.2. Upload
the patch as a separate file. I would include the subclass form in the
post to show the intneded effect, for discussion, and also so people can
test and us
Saturday eve (us, eastern).
Last night I had intermittent problems with bugs.python.org: issues not
being fetched, submissions not being recorded. David Abrahams reported
'bugs.python.org seems to be down' is his urlparse thread.
Right not, I have a fetch and submission 'loading' for over a mi
On 5/11/2010 7:16 PM, Antoine Pitrou wrote:
Apparently the tracker has been unresponding for some time now,
although port 80 still accepts connections.
As I reported before, there have been on and off problems for days.
Messages like (minutes ago) upon trying to login:
"Service Temporarily Un
On 5/13/2010 7:26 PM, Kiko Griffin wrote:
Dear Kiko - The python-dev mailing list and the gmane.comp.python.devel
mirror are for development of Python and CPython. Job announcements are
considered off-topic spam and constitute a dis-promotion for your firm.
Please do not repeat.
Please red
On 5/17/2010 2:59 PM, Bill Janssen wrote:
Yes, it would. As soon as I have working 3.x versions of BeautifulSoup,
PIL, ReportLab, JCC, pylucene, pyglet, nltk, email, epydoc, feedparser,
dictclient, docutils, hachoir, mutagen, medusa, python-dateutil, and
vobject, I'll let you know. :-)
There /
On 5/19/2010 6:13 PM, Yaniv Aknin wrote:
Hi,
I wanted to let python-dev know about a series of articles about
CPython's internals I'm publishing under the collective title "Guido's
Python"* (http://tech.blog.aknin.name/tag/guidos-python/).
This link has all post concatenated together in revers
On 5/20/2010 4:02 AM, Floris Bruynooghe wrote:
TypeError: invoked as a method, echo() takes exactly 1 argument (0 given)
captures the semantics, but is perhaps too verbose.
How about:
TypeError: bound method echo() takes exactly 1 argument (0 given)
That way you can also have: "unbound meth
On 5/20/2010 5:52 PM, Barry Warsaw wrote:
On May 20, 2010, at 12:53 PM, Guido van Rossum wrote:
Sounds good to me, since this is (a) a security fix that will make
some vendors happy, and (b) only a C-level API. I expect that some
apps embedding Python will use this API unconditionally and this
On 5/22/2010 8:06 PM, Jeffrey Yasskin wrote:
On Sat, May 22, 2010 at 4:12 PM, Brian Quinlan wrote:
Rename "executor" => "executer"
-1 for consistency with Java.
-10 for 'executer'. As far as I can find out, it is a misspelling of
'executor'. If the designers of some other language made a
On 26/05/10 20:57, Greg Ewing wrote:
(More generally, I'm inclined to think that introducing
a namespace package for a category of modules having
existing members in the stdlib is an anti-pattern,
As a user, I agree with this.
unless it's done during the kind of namespace refactoring
that
Mark Dickinson wrote (with interactice prompts removed)
code = """\
y = 3
def f():
return y
. f()
"""
exec code in {} # works fine
exec code in {}, {} # dies with a NameError
Traceback (most recent call last):
File "", line 1, in
File "", line 4, in
File "", line 3, in f
NameError:
I had the strong impression that there was a policy that x.y.z bugfix
releases should only fix bugs and not add new features and revise
current ones. The rationale, as I understood it, is that x.y.z releases
should be increasingly better implementations of a stable x.y feature
set. Adding featu
On 5/29/2010 6:39 AM, Antoine Pitrou wrote:
It is not the product of oversight.
I am actually glad, in a sense, that it was not casual whim. ;-)
I do not like the change, since it moves streams back further away from
Python's sequence model, but I withdraw the request for reversion in 3.1.3.
On 5/28/2010 11:41 PM, Nick Coghlan wrote:
However, it may be worth modifying the policy to ensure that such
exceptional bug fixes be mentioned prominently in the release notes and
on the download page for that maintenance release.
A sentence like "The behavior of it.X.truncate has been intent
On 5/29/2010 6:20 AM, Colin H wrote:
Perhaps the next step is to re-open the issue? If it is seen as a bug,
it would be great to see a fix in 2.6+ -
For the purpose of bugfix releases, a 'bug' is a discrepancy between doc
and behavior. Every new feature is seen as a 'design bug' by someone.
On 6/5/2010 10:55 AM, Guido van Rossum wrote:
I don't object (this had never occurred to me), but is Python on
Windows fully functioning when the registry is entirely ignored?
There have been a couple of portable CPython-on-a-CD or memory stick
that supposedly run on any machine without 'inst
On 6/9/2010 4:07 AM, Stephen J. Turnbull wrote:
Chris McDonough writes:
> It might be useful to copy the identifiers and URLs of all the backport
> request tickets into some other repository, or to create some unique
> state in roundup for these.
Closed issues are not lost. They can s
On 6/9/2010 10:42 AM, M.-A. Lemburg wrote:
>> Steve Holden wrote
How does throwing away information represent "moving forward"?
'Closing' a tracker issue does not 'throw away' information', it *adds*
information as to current intention.
It's certainly not fair to require all core developer
On 6/9/2010 7:45 AM, M.-A. Lemburg wrote:
Nick Coghlan wrote:
On 09/06/10 18:41, M.-A. Lemburg wrote:
The methods to be used will be .transform() for the encode direction
and .untransform() for the decode direction.
+1, although adding this for 3.2 would need an exception to the
moratorium ap
On 6/9/2010 8:17 AM, Antoine Pitrou wrote:
On Wed, 9 Jun 2010 13:57:05 +0200
Dirkjan Ochtman wrote:
On Wed, Jun 9, 2010 at 13:40, Antoine Pitrou wrote:
No, I don't think so. If I'm using hex "encoding", it's because I want
to see a text representation of some arbitrary bytestring (in order to
On 6/10/2010 2:48 AM, Senthil Kumaran wrote:
On Thu, Jun 10, 2010 at 6:40 AM, Alexandre Vassalotti
wrote:
On Wed, Jun 9, 2010 at 1:23 PM, "Martin v. Löwis" wrote:
Closing the backport requests is fine. For the feature requests, I'd only
close them *after* the 2.7 release (after determining t
On 6/10/2010 7:08 AM, M.-A. Lemburg wrote:
Walter Dörwald wrote:
The PEP would also serve as a reference back to both this discussion and
the previous one (which was long enough ago that I've forgotten most of it).
I too think that a PEP is required here.
Fair enough. I'll write a PEP.
T
On 6/18/2010 12:32 PM, Walter Dörwald wrote:
http://coverage.livinglogic.de/
I am a bit puzzled as to the meaning of the gray/red/green bars since
the correlation between coverage % and bars is not very high.
___
Python-Dev mailing list
Pytho
On 6/18/2010 10:24 AM, Jesse Noller wrote:
http://jessenoller.com/2010/05/20/announcing-python-sprint-sponsorship/
This does not specify what expenses you are thinking of covering. Food
is the most obvious.
Anyway, this got me to think about offering my house at a site for US
east coast mi
On 6/18/2010 6:51 PM, Raymond Hettinger wrote:
There has been a disappointing
lack of bug reports across the board for 3.x.
Here is one from this week involving the interaction of array and
bytearray. It needs a comment from someone who can understand the C-API
based patch, which is beyond me
After reading the discussion in the previous thread, signed in to
#python and verified that the intro message starts with a lie about
python3. I also verified that the official #python site links to "Python
Commandment Don't use Python 3… yet". The excuse that the negative
commandment site is n
On 6/19/2010 8:56 PM, Glyph Lefkowitz wrote:
> On Jun 19, 2010, at 5:39 PM, geremy condra wrote:
>
>> Bottom line, what I'd really like to do is kick them all off of
>> #python, but
>> practically I see very little that can be done to rectify the
>> situation at this
>> point.
Given the experienc
On 6/20/2010 6:35 AM, Laurens Van Houtven wrote:
I'm one of the active people in #python that some people dislike for
behavior with respect to Python 3.
As I wrote, I disliked the observable, written behavior, now changed.
You are obviously a fine person. We both love Python and have both
co
On 6/20/2010 3:59 PM, Jesse Noller wrote:
I suspect; if we were to keep pushing the concept of sponsored sprints
/ bounties on Python 3 library porting, we could see things pick up
donation wise. I've long suspected that there are companies out there
who do have funds, but lack a target, and don
On 6/20/2010 8:26 AM, Giampaolo Rodolà wrote:
I attempted to port pyftpdlib to python 3 several times and the
biggest show stopper has always been the bytes / string difference
introduced by Python 3 which forces you to *know* and *use* Unicode
every time you deal with some text and 2to3 is comp
On 6/20/2010 1:30 PM, Stephen J. Turnbull wrote:
The topic on #python seems unlikely to change at this point
I just verified that, thanks to Laurens and whoever, it has been.
It is now rather good.
Terry Jan Reedy
___
Python-Dev mailing list
Python-
On 6/20/2010 4:10 PM, Jesse Noller wrote:
On Sun, Jun 20, 2010 at 2:40 PM, P.J. Eby wrote:
While reading over this thread, I'm wondering whether at least my
(WSGI-related) problems in this area would be solved by the availability of
a type (say "bstr") that was simply a wrapper providing stri
On 6/20/2010 5:53 PM, Nick Coghlan wrote:
On Mon, Jun 21, 2010 at 7:12 AM, Simon de Vlieger wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In reply to the recent post by Laurens and the vow I made to change the text
which is presented on the python-commandments domain I have asked Lauren
On 6/20/2010 5:55 PM, Benjamin Peterson wrote:
2010/6/20 Antoine Pitrou:
On Sun, 20 Jun 2010 14:40:56 -0400
"P.J. Eby" wrote:
Actually, I would say that it's more that (in the network protocol
case) we *have* bytes, some of which we would like to *treat* as
text, yet do not wish to constantly
On 6/20/2010 9:33 PM, P.J. Eby wrote:
At 07:33 PM 6/20/2010 -0400, Terry Reedy wrote:
Do you have in mind any tools that could and should operate on both,
but do not?
From http://mail.python.org/pipermail/web-sig/2009-September/004105.html :
Thank for the concrete examples in this and your
On 6/21/2010 8:33 AM, Nick Coghlan wrote:
P.S. (We're going to have a tough decision to make somewhere along the
line where docs.python.org is concerned, too - when do we flick the
switch and make a 3.x version of the docs the default?
Easy. When 3.2 is released. When 2.7 is released, 3.2 beco
On 6/21/2010 11:31 AM, Arc Riley wrote:
Personally, I'd like to celebrate the upcoming Python 3.2 release (which
will hopefully include 3to2) with moving all packages which do not have
the 'Programming Language :: Python :: 3' classifier to a "Legacy"
section of PyPI and offer only Python 3 packa
On 6/20/2010 11:56 PM, Terry Reedy wrote:
The specific example is
>>> urllib.parse.parse_qsl('a=b%e0')
[('a', 'b�')]
where the character after 'b' is white ? in dark diamond, indicating an
error.
parse_qsl() splits that input on '=
On 6/21/2010 11:43 AM, Barry Warsaw wrote:
This is probably a stupid idea, and if so I'll plead Monday morning mindfuzz
for it.
Would it make sense to have "encoding-carrying" bytes and str types?
On 2009-11-5 I posted 'Add encoding attribute to bytes' to python-ideas.
It was shot down at th
On 6/21/2010 8:51 AM, Nick Coghlan wrote:
I don't know that the "all is well" camp actually exists. The camp
that I do see existing is the one that says "without a bug report,
inconsistencies in the standard library's unicode handling won't get
fixed".
The issues picked up by the regression te
On 6/21/2010 4:07 PM, Peng Yu wrote:
Hi,
Current pdf version of python documents don't have bookmarks for
sussubsection. For example, there is no bookmark for the following
section in python_2.6.5_reference.pdf. Also the bookmarks don't have
section numbers in them. I suggest to include the sect
On 6/21/2010 3:59 PM, Steve Holden wrote:
Terry Reedy wrote:
On 6/21/2010 8:33 AM, Nick Coghlan wrote:
P.S. (We're going to have a tough decision to make somewhere along the
line where docs.python.org is concerned, too - when do we flick the
switch and make a 3.x version of the doc
On 6/21/2010 1:29 PM, P.J. Eby wrote:
At 05:49 PM 6/21/2010 +0100, Michael Foord wrote:
Why is your proposed bstr wrapper not practical to implement outside
the core and use in your own libraries and frameworks?
__contains__ doesn't have a converse operation, so you can't code a type
that work
On 6/21/2010 1:29 PM, Guido van Rossum wrote:
Actually, the big problem with Python 2 is that if you mix str and
unicode, things work or crash depending on whether any of the str
objects involved contain non-ASCII bytes.
If one API decides to upgrade to Unicode, the result, when passed to
anoth
On 6/21/2010 1:58 PM, Stephen J. Turnbull wrote:
As for "Think Carefully About It Every Time", that is required only in
Porting Programs That Mix Operation On Bytes With Operation On Str.
The 2.x anti-pattern
If you write programs from scratch, however, the decode-process-encode
paradigm qui
On 6/21/2010 2:46 PM, P.J. Eby wrote:
This ignores the existence of use cases where what you have is text that
can't be properly encoded in unicode.
I think it depends on what you mean by 'properly'. I will try to explain
with English examples.
1. Unicode represents a finite set of characte
On 6/22/2010 1:22 AM, Glyph Lefkowitz wrote:
The thing that I have heard in passing from a couple of folks with
experience in this area is that some older software in asia would
present characters differently if they were originally encoded in a
"japanese" encoding versus a "chinese" encoding, e
On 6/22/2010 9:24 AM, Michael Urman wrote:
By idempotent-when-possible, I mean to_bytes(str_or_bytes, encoding,
errors) that would pass an instance of bytes through, or encode an
instance of str. And of course a to_str that performs similarly,
passing str through and decoding bytes. While bytes(
On 6/22/2010 12:53 PM, Guido van Rossum wrote:
On Mon, Jun 21, 2010 at 11:47 PM, Raymond Hettinger
wrote:
On Jun 21, 2010, at 10:31 PM, Glyph Lefkowitz wrote:
This is a common pain-point for porting software to 3.x - you had a
string, it kinda worked most of the time before, but now you n
On 6/22/2010 6:52 AM, Steven D'Aprano wrote:
On Tue, 22 Jun 2010 11:46:27 am Terry Reedy wrote:
3. Unicode disclaims direct representation of glyphic variants
(though again, exceptions were made for asian acceptance). For
example, in English, mechanically printed 'a' and 'g
Tres, I am a Python3 enthusiast and realist. I did not expect major
adoption for about 3 years (more optimistic than the 5 years of some).
If you are feeling pressured to 'move' to Python3, it is not from me. I
am sure you will do so on your own, perhaps even with enthusiasm, when
it will be g
On 6/23/2010 7:28 AM, Cesare Di Mauro wrote:
sorry, I made a mistake, assuming that the project was known.
A common mistake of people who announce their projects ;-)
Someone recently make the same mistake on python-list with respect to a
'BDD' package (the Wikipedia suggests about 6 possible
On 6/24/2010 1:38 PM, Bill Janssen wrote:
Secondly, maybe the string situation in 2.x wasn't as broken as we
thought it was. In particular, those who deal with lots of encoded
strings seemed to find it handy, and miss it in 3.x. Perhaps strings
are more like numbers than we think. We have sep
On 6/24/2010 4:59 PM, Guido van Rossum wrote:
But I wouldn't go so far as to claim that interpreting the protocols
as text is wrong. After all we're talking exclusively about protocols
that are designed intentionally to be directly "human readable"
I agree that the claim "':' is just a byte" i
On 6/24/2010 8:31 PM, Stephen Thorne wrote:
Oh, I thought this was quite clear. I was specifically meaning the large
"Python 2 or 3" button on python.org. It would help users who want to know
what version of python to use if they had a clear guide as to what version
to download.
I think everyo
On 6/24/2010 8:51 PM, Rich Healey wrote:
http://docs.python.org/library/copy.html
Discussion of the wording of current docs should go to python-list.
Py-dev is for development of future Python.
--
Terry Jan Reedy
___
Python-Dev mailing list
Pytho
The several posts in this and other threads go me to think about text
versus number computing (which I am more familiar with).
For numbers, we have in Python three builtins, the general purpose ints
and floats and the more specialized complex. Two other rational types
can be imported for speci
On 6/27/2010 5:44 AM, Georg Brandl wrote:
Am 22.06.2010 01:01, schrieb Terry Reedy:
On 6/21/2010 3:59 PM, Steve Holden wrote:
Terry Reedy wrote:
On 6/21/2010 8:33 AM, Nick Coghlan wrote:
P.S. (We're going to have a tough decision to make somewhere along the
line where docs.python.o
Sure. Since I expect that the argument for treating 3.2 as a regular
production-use-ready release will be stronger then than now, I agree on
differing discussion.
I meant 'deferring'
--
Terry Jan Reedy
___
Python-Dev mailing list
Python-Dev@python.
On 7/2/2010 12:43 AM, Glyph Lefkowitz wrote:
def f(): return 1 + "1"
instead of compiling something which can't fail to raise an
exception, would that still be a legal Python implementation?
I'd say "no". Python has defined semantics in this situation: a
TypeError is raised.
The manuals ar
On 7/3/2010 10:34 AM, Christian Heimes wrote:
Which docs did you look at specifically that said "and newer"? That
would be a bug.
The readme.txt in the PCbuild directory contains the sentence "Microsoft
Visual C++ 2008 Express Edition is required at the very least". The
wording could be interp
On 7/3/2010 12:36 PM, Tres Seaver wrote:
I would say that using the SVN mirror is a fine way to experiment with
using hg against the Python sources to develop and test patches. Here
is the setup I have used for work against trunk (I have a parallel pair
of repositories for the release2.6-maint
On 7/4/2010 2:31 AM, Éric Araujo wrote:
But Python tests lack coverage stats, so it is hard to say anything.
FYI: http://coverage.livinglogic.de/
Turns out the audioop is one of the best covered modules, at 98%
--
Terry Jan Reedy
___
Python-Dev m
I think there are a couple of potential action items that have come out
of the discussion.
1. Python License
If there is not already, could there be an explanatory note, something
like (worded to be 'neutral':
"The Python License is complicated because Python has been developed at
various t
[Also posted to http://bugs.python.org/issue2986
Developed with input from Eli Bendersky, who will write patchfile(s) for
whichever change option is chosen.]
Summary: difflib.SeqeunceMatcher was developed, documented, and
originally operated as "a flexible class for comparing pairs of
sequenc
On 7/6/2010 3:59 PM, Alexander Belopolsky wrote:
I am more interested in Brett's overall vision than this particular
module. I understand that to be one of a stdlib that is separate from
CPython and is indeed the standard Python library.
Questions:
!. Would the other distributions use a stan
On 7/7/2010 3:32 PM, Brett Cannon wrote:
That's the idea. We already have contributors from the various VMs who
has commit privileges, but they all work in their own repos for
convenience. My hope is that if we break the stdlib out into its own
repository that people simply pull in then other VM
On 7/7/2010 4:11 PM, Tres Seaver wrote:
Antoine Pitrou wrote:
On Wed, 7 Jul 2010 19:44:31 +0200
Eli Bendersky wrote:
For what it's worth, my benchmarking showed that modifying the
heuristic to only kick in when there are more than 100 kinds of
elements (Terry's option A) didn't affect the run
I had considered the possibility of option A for 2.7 and A & C for 3.2.
But see below.
Since posting, I did an experiment with a 700 char paragraph of text
(the summary from the post) compared to an 'edited' version. I did the
comparision with and without the current heuristic. I did not not
1201 - 1300 of 2504 matches
Mail list logo
