Raymond Hettinger added the comment:
As Antoine and Eric stated, the module is working as intended and we don't
document implementation details and generally stay away from talking about
performance in the docs.
--
resolution: -> rejected
status: open -
Raymond Hettinger added the comment:
> Raymond, do we care whether or not the
> pure Python version of functools.partial
> supports inheritance and instance testing?
We don't care. The docs make very few
guarantees beyond the core functionality.
Everything else is an impleme
Raymond Hettinger added the comment:
Thanks for the link :-)
--
___
Python tracker
<http://bugs.python.org/issue7117>
___
___
Python-bugs-list mailing list
Unsub
Raymond Hettinger added the comment:
-1 on complicating the API. The purported problem isn't pervasive enough to
warrant a change (I frequently teach python classes and do code reviews and
rarely encounter this issue). Also, the proposed change isn't going to help
the peop
Raymond Hettinger added the comment:
FWIW, I don't think this is worth further disruption. We already have an
excellent set of float repr routines. There is no problem to be solved here.
--
assignee: -> rhettinger
priority: normal -> low
versions:
Raymond Hettinger added the comment:
The docs are clear on this topic. No doc change can help someone who skips
reading the docs and assumes the method does something different.
--
resolution: -> rejected
status: open -> closed
___
Python t
Changes by Raymond Hettinger :
--
assignee: -> rhettinger
nosy: +rhettinger
priority: normal -> low
___
Python tracker
<http://bugs.python.org/i
Raymond Hettinger added the comment:
I concur with Mark. This is a very challenging area and no change would be
warranted without keeping the current accuracy guarantees, definitive speed
improvement, extensive tests, and consideration of the impact on users of
having float reprs change yet
Raymond Hettinger added the comment:
Please stick with "integer" instead of "decimalinteger". In an effort to make
the docs more precise, there is an unintended effect of making them harder to
understand.
--
nosy: +rhettinger
__
Changes by Raymond Hettinger :
--
priority: normal -> high
___
Python tracker
<http://bugs.python.org/issue12508>
___
___
Python-bugs-list mailing list
Un
Changes by Raymond Hettinger :
--
assignee: -> rhettinger
nosy: +rhettinger
___
Python tracker
<http://bugs.python.org/issue12514>
___
___
Python-bugs-list mai
Raymond Hettinger added the comment:
Thank you. The patch looks correct. I will apply it as soon as I get a chance.
--
___
Python tracker
<http://bugs.python.org/issue12
Raymond Hettinger added the comment:
The current glossary entry is fine and encompasses was is ordinarily meant by
attribute as distinct from a method.
We sometimes use the term loosely to mean any value whether callable or not.
And sometimes it is used loosely to mean anything that can be
Changes by Raymond Hettinger :
--
resolution: -> rejected
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue12491>
___
___
Python-bugs-
Raymond Hettinger added the comment:
IIRC, classes weren't supposed to be able inherit from two classes that had
different metaclasses (since differing metaclasses don't necessarily play well
with one another).
--
nosy: +rhettinger
Changes by Raymond Hettinger :
--
assignee: -> rhettinger
priority: normal -> low
___
Python tracker
<http://bugs.python.org/issue5996>
___
___
Python-bugs-
Changes by Raymond Hettinger :
--
resolution: -> accepted
___
Python tracker
<http://bugs.python.org/issue12542>
___
___
Python-bugs-list mailing list
Un
Raymond Hettinger added the comment:
index() isn't supported.
--
assignee: -> rhettinger
resolution: -> invalid
status: open -> closed
___
Python tracker
<http://bugs.pyth
New submission from Raymond Hettinger :
gzip.open() should parallel file.open() so that that zipped files can be read
in the same way as regular files:
for line in gzip.open('notes.txt', 'r', encoding='latin-1'):
print(line.rstrip())
--
components:
Changes by Raymond Hettinger :
--
versions: -Python 3.2
___
Python tracker
<http://bugs.python.org/issue12559>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Raymond Hettinger :
--
assignee: georg.brandl -> rhettinger
nosy: +rhettinger
versions: +Python 3.3 -Python 3.1
___
Python tracker
<http://bugs.python.org/issu
Raymond Hettinger added the comment:
The example is correct and runs as expected:
>>> Decimal(3.14)
Decimal('3.140124344978758017532527446746826171875')
Per the Whatsnew3.2 document:
'''
The decimal.Decimal constructor now accepts float objects
Raymond Hettinger added the comment:
Éric, this is not a doc bug. The sequence ABCs do not require slicing support.
--
___
Python tracker
<http://bugs.python.org/issue12
Raymond Hettinger added the comment:
-1
Array's API much more closely matches that of list than it does numpy's arrays
which are profoundly different. So we should stick the one-way-to-do-it idiom:
array.array('c', '\0') * 100 or array.array('d', [
Raymond Hettinger added the comment:
To my eye, this looks like a bytearray API bug in the bytearray implementation.
ISTM, the rhs of a slice assignment needs to be restricted to iterable inputs.
I'm marking this as low priority because the documented behaviors (i.e. normal
slice assig
Changes by Raymond Hettinger :
--
priority: normal -> high
___
Python tracker
<http://bugs.python.org/issue12613>
___
___
Python-bugs-list mailing list
Un
Raymond Hettinger added the comment:
Looks good.
Thx.
--
assignee: -> rhettinger
nosy: +rhettinger
___
Python tracker
<http://bugs.python.org/issu
Raymond Hettinger added the comment:
The proposed rewrite doesn't make any sense to me. Also "set through" is an
reads awkwardly.
--
assignee: docs@python -> rhettinger
nosy: +rhettinger
___
Python tracker
<http://bugs.
Raymond Hettinger added the comment:
Array has been around for a very long time and this functionality has never
been requested. That and the fact that we already have a way to do it (the
same way as for lists) is a strong indication that this isn't needed at all.
--
resol
New submission from Raymond Hettinger :
Currently bool(None) returns False only because it has a special case in
PyObject_IsTrue(). All other types can become False only if they implement
__bool__() or __len__().
I propose removing the special case branch and instead adding __bool__ to None
Changes by Raymond Hettinger :
--
keywords: +patch
Added file: http://bugs.python.org/file22781/none_bool.diff
___
Python tracker
<http://bugs.python.org/issue12
Changes by Raymond Hettinger :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue12647>
___
___
Python-bugs-
Raymond Hettinger added the comment:
Thanks for the bug report and patch.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
Changes by Raymond Hettinger :
--
assignee: docs@python -> rhettinger
nosy: +rhettinger
___
Python tracker
<http://bugs.python.org/issue12668>
___
___
Python-
Raymond Hettinger added the comment:
See also #12631 regarding the remove() method for bytearray.
--
___
Python tracker
<http://bugs.python.org/issue12
Changes by Raymond Hettinger :
--
assignee: docs@python -> rhettinger
nosy: +rhettinger
___
Python tracker
<http://bugs.python.org/issue12666>
___
___
Python-
Raymond Hettinger added the comment:
Thanks, I'll fix that shortly.
--
priority: normal -> high
___
Python tracker
<http://bugs.python.org/issue12717>
___
Raymond Hettinger added the comment:
Fixed. Thanks for the report.
Éric, the test suite didn't catch this because the error wasn't user visible --
the chainmap is only used internally and only __getitem__ was needed.
--
resolution: -> fixed
status: o
Raymond Hettinger added the comment:
I think the patch is correct.
FWIW, my style is to prebind the next method, making the counter completely
self-contained (like a closure):
+_counter = itertools.count().next
def _newname(template="Thread-%d"):
global _counter
-
Raymond Hettinger added the comment:
How about __len__()?
--
nosy: +rhettinger
___
Python tracker
<http://bugs.python.org/issue12740>
___
___
Python-bugs-list m
Changes by Raymond Hettinger :
--
assignee: -> rhettinger
priority: normal -> low
___
Python tracker
<http://bugs.python.org/issue12740>
___
___
Pyth
Raymond Hettinger added the comment:
Nice.
--
nosy: +rhettinger
___
Python tracker
<http://bugs.python.org/issue12744>
___
___
Python-bugs-list mailing list
Unsub
Raymond Hettinger added the comment:
In general, I think we can prevent confusion about the meaning of __len__ by
sticking to the general rule: len(object)==len(list(obj)) for anything that
produces an iterable result. In the case of struct, that would be the length
of the tuple returned
Raymond Hettinger added the comment:
Are you sure this should have been backported? Are there any apps that may be
working now but won't be after the next point release?
--
nosy: +rhettinger
___
Python tracker
<http://bugs.python.org/is
Raymond Hettinger added the comment:
Right. I was looking at the other patches that went in in the last 24 hours.
--
___
Python tracker
<http://bugs.python.org/issue12
New submission from Raymond Hettinger :
While keeping the MT generator as the default, add new alternative random
number generators as drop-in replacements. Since MT was first introduced, PRNG
technology has continued to advance.
I'm opening this feature request to be a centralized pla
Raymond Hettinger added the comment:
Please focus your thoughts.
--
___
Python tracker
<http://bugs.python.org/issue12754>
___
___
Python-bugs-list mailin
Changes by Raymond Hettinger :
--
assignee: -> rhettinger
nosy: +rhettinger
___
Python tracker
<http://bugs.python.org/issue12793>
___
___
Python-bugs-list mai
Raymond Hettinger added the comment:
Nick, I still want to work on this one.
--
___
Python tracker
<http://bugs.python.org/issue11816>
___
___
Python-bugs-list m
Raymond Hettinger added the comment:
On python-dev a few month ago, Guido agreed with you that this is an arbitrary
limitation that should be removed at some point. In particular, he worried
that programmatically generated code would tend to run into this limitation.
--
nosy
Raymond Hettinger added the comment:
Running python with the -3 command line option will warn about Python 3.x
incompatibilities that 2to3 cannot trivially fix.
--
nosy: +rhettinger
___
Python tracker
<http://bugs.python.org/issue12
Raymond Hettinger added the comment:
> some simple examples showing the syntax would go a long way.
Sorry, there as just too many ways to go and we are intentionally not stating
which way is preferred. I've seen many variants a:[Integral] for a list of
integers, a:(int,str) for a
Raymond Hettinger added the comment:
I would like to be involved in the design of the API for a UCA module and its
routines for loading Unicode Collation Element Tables (not making the mistake
of using global state like the locale module does).
--
nosy: +rhettinger
Raymond Hettinger added the comment:
Thanks Douglas. Can you say what the cryptographic guarantees are for Chacha
and Salsa (seeing a stream of randoms doesn't allow you to do deduce internal
state, previous randoms, or future randoms)? Is it suitably strong for gaming
(dealing
Changes by Raymond Hettinger :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue12793>
___
___
Python-bugs-list mailing list
Unsubscri
Raymond Hettinger added the comment:
+1
--
assignee: nadeem.vawda -> rhettinger
___
Python tracker
<http://bugs.python.org/issue12909>
___
___
Python-bugs-lis
Changes by Raymond Hettinger :
--
assignee: -> rhettinger
___
Python tracker
<http://bugs.python.org/issue12941>
___
___
Python-bugs-list mailing list
Un
Changes by Raymond Hettinger :
--
assignee: -> rhettinger
nosy: +rhettinger
___
Python tracker
<http://bugs.python.org/issue12914>
___
___
Python-bugs-list mai
Raymond Hettinger added the comment:
A few thoughts:
* no one has ever made a request for this
* different people may want to do it in different ways
(the formulas are hard-wired).
* the '...' connector is hardwired
(perhaps ' ... ' would look less odd).
* we should h
Changes by Raymond Hettinger :
--
resolution: -> rejected
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue12914>
___
___
Python-bugs-
Changes by Raymond Hettinger :
--
assignee: -> rhettinger
nosy: +rhettinger
___
Python tracker
<http://bugs.python.org/issue12917>
___
___
Python-bugs-list mai
Changes by Raymond Hettinger :
--
assignee: -> rhettinger
nosy: +rhettinger
___
Python tracker
<http://bugs.python.org/issue12916>
___
___
Python-bugs-list mai
Raymond Hettinger added the comment:
Resist the urge to fatten APIs until you're sure that:
* they are needed
* they are well developed (many internal utils fail this test)
* they are worth the extra time it takes to learn what is in a module (adding
rarely needed tools has the side-effe
Raymond Hettinger added the comment:
This can be done for Py3.2. It completes needed functionality for string
formatting which is something we all want to take hold and is necessary for the
3.x series to succeed.
--
versions: +Python 3.2 -Python 3.3
Raymond Hettinger added the comment:
Am rejecting this feature request because of the concerns mentioned in the post
on 4/3. The current requirement for explicit forwarding may be slightly
inconvenient to type but it does add provide clarity that the method should be
applied to the next-in
Changes by Raymond Hettinger :
--
assignee: -> rhettinger
priority: normal -> low
___
Python tracker
<http://bugs.python.org/issue1479611>
___
___
Pyth
Raymond Hettinger added the comment:
ISTM the space saving of value of __slots__ isn't typically needed in the
context of variable length built-in types.
Guido has long regarded __slots__ as a confusing hack. That should warn us
away for extending its functionality.
Unless there are
Raymond Hettinger added the comment:
The moratorium only includes builtins and certainly does not apply to pure
python modules (other implementations see those benefits immediately and it
does not interfere with their getting caught-up).
FWIW, I'm +1 on the basic idea.
--
key
Raymond Hettinger added the comment:
Fixing-up str formatting idiosyncracies does not fall under the moratorium and
is helpful in getting 3.x to be usable.
That being said, I'm not convinced that this is actually a helpful feature.
Not all objects supporting __getitem__ offer suppor
Raymond Hettinger added the comment:
+1 on the basic idea to make error messages more informative where possible,
but am not sure how it would work in any but the more simple cases.
How would work in cases where there are multiple possible "expected" tokens?
>
Raymond Hettinger added the comment:
I do not believe that this is covered by the moratorium. It's important for
3.x success to get new string formatting to its highest state of usability.
Matching published standards and practices(i.e. C99) and improving ability to
convert from old-
Changes by Raymond Hettinger :
--
priority: normal -> low
stage: unit test needed ->
___
Python tracker
<http://bugs.python.org/issue3489>
___
___
Pyth
Changes by Raymond Hettinger :
--
assignee: -> rhettinger
nosy: +rhettinger
priority: normal -> low
versions: +Python 3.3 -Python 3.2
___
Python tracker
<http://bugs.python.org/iss
Raymond Hettinger added the comment:
I think this falls under the language moratorium in that it requires core
changes that make it more difficult for other implementations to catch-up.
--
nosy: +rhettinger
versions: +Python 3.3 -Python 3.2
Changes by Raymond Hettinger :
--
priority: normal -> low
___
Python tracker
<http://bugs.python.org/issue1158231>
___
___
Python-bugs-list mailing list
Un
Raymond Hettinger added the comment:
I concur with Terry.
This is just a fact of life when subclassing builtins.
The objects are "open-for-extension, closed-for-modification".
If you want more direct control use UserDict.
--
nosy: +
Raymond Hettinger added the comment:
FWIW, we should be cautious about documenting all behaviors. It is arguable
that this was an implementation detail and not a guaranteed behavior. As soon
as you document it, people will rely on the API and all other implementations
will need to change
Raymond Hettinger added the comment:
Declaring YAGNI and closing.
Thanks Michael.
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue1
Raymond Hettinger added the comment:
FWIW, the $name $$ $(name) convention is used many other contexts and I don't
think there is usually support provided to not substitute $$. Even if there
were, there is a usability issue where the final substitution needs to be
applied differently t
Raymond Hettinger added the comment:
This request seems reasonable.
--
keywords: +easy
nosy: +rhettinger
___
Python tracker
<http://bugs.python.org/issue3
Raymond Hettinger added the comment:
Am rejecting this request because it complicates pprint and makes it harder to
extend. Most use cases of pprint either don't need this or have output
requirements more complicated than proposed (i.e. adding fixed width columns
for tabular output
Raymond Hettinger added the comment:
These synonyms have been around a very long time and many test suites have one
or the other or both. Nothing good can come from breaking those existing test
suites. We don't need to harm our users just to accommodate a stylistic
prefe
Raymond Hettinger added the comment:
What a tremendous waste of time and inane exercise. AFAICT, this is a zero
value add.
Also, we try to avoid these sort of search-and-replace exercises because 1)
they are not part of holistic refactoring (Guido's term for making changes
while y
Raymond Hettinger added the comment:
Thank you. Please do the reversion and the docstring fixup.
--
___
Python tracker
<http://bugs.python.org/issue5
Raymond Hettinger added the comment:
Please don't pursue this further. It does not matter at all whether developers
use assertEqual or assertEquals. That is no more than a stylistic preference.
I do not want a commit hook, or for developer patches to be edited, or for
there to
Raymond Hettinger added the comment:
I'm rejecting this feature request on the grounds that the use cases are
sufficiently uncommon to warrant adding API complexity.
Currently, the notions of reverse() and sort() are comparatively simple. They
correspond well to what I see in
Raymond Hettinger added the comment:
You're welcome :-)
--
___
Python tracker
<http://bugs.python.org/issue7734>
___
___
Python-bugs-list mailing list
Raymond Hettinger added the comment:
Antoine, thanks for posting these.
--
___
Python tracker
<http://bugs.python.org/issue9612>
___
___
Python-bugs-list mailin
Raymond Hettinger added the comment:
The effort to backport dictviews was incomplete.
Fixed in r84148.
Thanks for the report.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Raymond Hettinger added the comment:
Can you provide links to the other requests?
This seems to be at odds with the whole premise
of what Queue.join() is trying to do (wait until
all worker threads have marked their tasks as done).
--
assignee: -> rhettinger
nosy: +rhettin
Raymond Hettinger added the comment:
FWIW, if you want to do other tasks in a main thread and need to check on the
status task completion in worker threads, you can already loop on:
while q.unfinished_tasks:
do_other_fun_stuff()
q.join() # this shouldn't
Raymond Hettinger added the comment:
One of the provided links is duplicate (repost from StackOverflow). None of
the links offer use cases which can be used to inform the design (i.e. is this
the correct approach, should a timeout raise a RuntimeError like
Condition.wait() does, should a
Raymond Hettinger added the comment:
I will leave this open for a while.
It may be that it is a good idea
and that some good use cases will
emerge to inform a correct design.
In the meantime, it would be great
if you could post your subclass to
the ASPN Cookbook to collect feedback
Raymond Hettinger added the comment:
I concur with Nick. If you want to develop your __DECORATORS__ idea further,
it should be done off-list. ISTM, this is more of a shot in the dark than a
concrete plan to solve known, real problems.
--
resolution: -> rejected
status: o
Changes by Raymond Hettinger :
--
assignee: stutzbach -> rhettinger
___
Python tracker
<http://bugs.python.org/issue8750>
___
___
Python-bugs-list mai
Raymond Hettinger added the comment:
This needs to stay rejected. I'm unwilling to introduce special cases in the
language just to support a peephole optimization.
--
assignee: gvanrossum -> rhettinger
___
Python tracker
<http://bugs
Raymond Hettinger added the comment:
The was a nice attempt at a peephole optimization.
I'm rejecting it because:
* too many other things need to be changed to support it
* the measured win is somewhat small
* we have a negative bias towards expanding the peephole optimizer
* the AST may
Raymond Hettinger added the comment:
I support adding index() and count() to range objects.
--
___
Python tracker
<http://bugs.python.org/issue9213>
___
___
Pytho
Raymond Hettinger added the comment:
The patch looks good.
Feel free to apply.
--
assignee: rhettinger -> stutzbach
___
Python tracker
<http://bugs.python.org/iss
Raymond Hettinger added the comment:
Fixed in r84252, r84252, and r84254.
--
priority: high -> normal
resolution: accepted -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.o
401 - 500 of 9609 matches
Mail list logo
