Walter Doekes added the comment:
The handlers are AFAIK referenced - if you peek at logging._handlerList or
logging._handlers you should see them in there.
Aha. But that's the point. They aren't. If they were, I wouldn't have any
problems with this. But I have this problem because the
Raymond Hettinger added the comment:
These edits look reasonable, useful and correct.
--
nosy: +rhettinger
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23006
___
Raymond Hettinger added the comment:
Guido, do you care to close this one?
Terry, has channeled you and thinks it may be against your wishes to turn sum()
into a general purpose sequence concatenator. I also seem to recall you
expresses similar thoughts back when Alex Martelli first
Mark Dickinson added the comment:
Sergey: do you have an example of the Lib/bisect.py code causing problems in
real (non-contrived) code? If not, I'd suggest closing this report as not a
bug.
--
___
Python tracker rep...@bugs.python.org
Raymond Hettinger added the comment:
[Serhiy]
So what to do wish UserDict?
I'm leaning in favor of leaving UserDict as-is. AFAICT, in the very long
history of UserDict, this has never been a problem. So, I don't think there is
an issue worth breaking the published API and possibly
Raymond Hettinger added the comment:
-1 on moving this to builtin status. For a long time, we've tried to keep a
back pressure against adding more builtins (in part because it increases the
learning curve for the core language). The SimpleNamespace() type would need
to become *much* more
Raymond Hettinger added the comment:
This change looks reasonable and correct.
--
nosy: +rhettinger
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23005
___
Vinay Sajip added the comment:
Aha. But that's the point. They aren't.
Ok, I'll investigate further. Thanks for your persistence :-)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23010
Bruno Cauet added the comment:
There's a small typo in the comments:
+# make sure cmd.link_objects is turned into a list
+# is it's a string
Should be:
+# make sure cmd.link_objects is turned into a list
+# if it's a string
--
nosy: +bru
Serhiy Storchaka added the comment:
Here is a patch similar to patch from issue22609 which makes
WeakValueDictionary constructor and update accept keyword arguments self and
dict.
--
keywords: +needs review, patch
stage: - patch review
Added file:
Changes by Mark Dickinson dicki...@gmail.com:
--
resolution: - not a bug
status: open - pending
versions: +Python 3.4 -Python 3.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23007
___
Raymond Hettinger added the comment:
[John Posner]
The fact is that a programmer using defaultdict does not need
to know anything about __missing__.
I disagree. It seems to help people understand the defaultdict which otherwise
seems more magical that it actually is. Also, it is a part of
Raymond Hettinger added the comment:
I agree with Mark. This code is *very* old and AFAICT it has never caused a
problem in practice.
The textbook formula is more important in languages without something like
Python long ints. In Python, textbook form just slows down and obfuscates
the
Raymond Hettinger added the comment:
I think the first half of the sentence is enough:
“For mappings, it should iterate over the keys of the container.”
That should do it :-)
--
nosy: +rhettinger
___
Python tracker rep...@bugs.python.org
Raymond Hettinger added the comment:
I would think that the PY_SSIZE_T_MAX check belongs inside the:
if (result != NULL) {
it-it_index++;
return result;
}
just before the increment which could cause the overflow. Also, PY_SSIZE_T_MAX
is a valid value to pass to
Raymond Hettinger added the comment:
I'd prefer to just reimplement itemgetter and attrgetter to make
them picklable rather than adding pickling methods to them;
see attached patch.
That isn't the usual approach. The pickling methods are there for a reason. I
prefer to leave the existing
Raymond Hettinger added the comment:
Please remember that a potential new pickling feature is the least import part
of the design of methodcaller, itemgetter, and attrgetter. Pickle support
should be driven by the design rather become a predominant consideration.
One other note: the OP's
Serhiy Storchaka added the comment:
This doesn't matter because next() will raise an exception if it_index ==
PY_SSIZE_T_MAX in any case. The code should be changed much more to allow
yielding an item with index PY_SSIZE_T_MAX, use other (negative) signal value
and change the behavior of
Raymond Hettinger added the comment:
http://svn.python.org/view/python/branches/release25-maint/Doc/lib/libcollections.tex?r1=38658r2=42573
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9536
Clement Rouault added the comment:
Also, PY_SSIZE_T_MAX is a valid value to pass to PySequence_GetItem(), so it
shouldn't be blocked unless necessary.
I agree with you, that's why my first path was checking at the next call if
it-it_index had overflowed. But then it relies on undefined
STINNER Victor added the comment:
I prefer to raise an OverflowError *before* calling
PySequence_GetItem(). The call to PySequence_GetItem() may be
expensive, and we have to drop the result if an OverflowError is
raised after the call. At the end, the behaviour is the same: an
OverflowError is
Serhiy Storchaka added the comment:
Here is a patch. 2.7 is affected too.
--
keywords: +patch
nosy: +serhiy.storchaka
stage: - patch review
type: crash - behavior
versions: +Python 2.7, Python 3.5 -Python 3.2, Python 3.3
Added file:
Changes by Serhiy Storchaka storch...@gmail.com:
--
nosy: +georg.brandl
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23017
___
___
Serhiy Storchaka added the comment:
Instead, it is the picking and unpickling tools themselves that tend to have
crummy error messages when presented with objects that weren't specially
designed with pickle support.
See issue22995 about this.
--
stockbsd Li added the comment:
1. py2 is unaffected, because stderr/stdout is not None in py2's pythonw and
the catch works correctly.
2. as to py3, I prefer this patch:
- execpt OSError:
+ execpt:
--
___
Python tracker rep...@bugs.python.org
New submission from Amaury Forgeot d'Arc:
When an extension module is compiled with CPython3.4, the nb_matrix_multiply
slot is not filled, and no memory is allocated for it.
If the extension module is imported by CPython3.5, nb_matrix_multiply contains
garbage and segfaults the interpreter.
Changes by Antoine Pitrou pit...@free.fr:
--
priority: normal - release blocker
versions: +Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23020
___
Amaury Forgeot d'Arc added the comment:
Here is a test module that segfaults on Python3.5.
It's derived from _testcapi, but it can be anything with a PyNumberMethods.
I compiled with
gcc -g -I path/to/cpython3.4/Include/ -I /path/to/cpython3.4 mytest.c -fPIC
--shared -o mytest.so
Then I
STINNER Victor added the comment:
+ execpt:
Please never use that, but except Exception: instead to not catch SystemExit
or KeyboardInterrupt.
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23016
Walter Dörwald added the comment:
The updated code in the documentation still doesn't set the * and **
parameters. I would have preferred the following code:
for param in sig.parameters.values():
if param.name not in ba.arguments:
if param.kind is inspect.Parameter.VAR_POSITIONAL:
Changes by Serhiy Storchaka storch...@gmail.com:
--
keywords: +easy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22883
___
___
Python-bugs-list
Bruno Cauet added the comment:
Here is a simple fix for the issue, plus a test.
It does not break any unit test but this raises a backwards-compatibility
problem. Therefore I wouldn't advise using it for Python 3.4 but only 3.5+.
--
keywords: +patch
nosy: +bru
versions: +Python 3.5
Rishi added the comment:
There is indeed a test failure that occurs without the patch. This is a new
test I had added.
The reason is that in the existing implementation, when a boundary does not
exist, the implementation does not include the trailing CRLF, LF or for that
matter CR as part of
R. David Murray added the comment:
That's a bug (you will note that it causes a test failure in the email test
suite). - means this date is in UTC, but that may or may not be the local
timezone of the message. + means this date really is in the UTC
timezone. utils.format_datetime
Rishi added the comment:
One of my comments shot the wrapped line limit. Also changed the test in
question to check the lengths of the expected and actual buffer to checking the
contents of the respective buffers.
--
Added file: http://bugs.python.org/file37400/issue1610654_5.patch
Brett Cannon added the comment:
Fair enough. I have no qualms with keeping importlib.util.module_from_spec()
and have Loader.create_module() just call module_from_spec().
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23014
Benjamin Peterson added the comment:
This technically falls under the fact that we don't have ABI compatibility
between 3.N and 3.(N + 1).
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23020
R. David Murray added the comment:
This is a bit of a conundrum. Our (string module) definition of printable is
very clear, and it includes the other whitespace characters.
We could document that this does not match the posix definition of printable.
It also does not match the RFC 5822
R. David Murray added the comment:
The API is what it is. In the Python3 docs this is documented as a backward
compatibility issue, and the workaround using the new errors.codes is provided.
For 2.7 we are stuck with what we have, since we don't add new features to 2.7.
--
nosy:
Changes by STINNER Victor victor.stin...@gmail.com:
--
components: +Unicode
nosy: +ezio.melotti, haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23017
___
Raymond Hettinger added the comment:
The call to PySequence_GetItem() may be expensive, and we have to drop
the result if an OverflowError is raised after the call.
You do realize that this error will be very rare and therefore inconsequential.
--
Dmitry Shachnev added the comment:
Thanks, I did not know that. Here is version 3.
--
Added file: http://bugs.python.org/file37402/issue22932_v3.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22932
New submission from Berker Peksag:
See issue 22883 for a similar issue.
Modules/_io/_iomodule.h:72:/* Printing a variable of type off_t (with e.g.,
PyString_FromFormat)
Modules/_json.c:708:/* Read a JSON array from PyString pystr.
Modules/_json.c:781:/* Read a JSON constant from
Tom Tanner added the comment:
This is actually more complicated than I initially thought.
According to
https://www.python.org/dev/peps/pep-/#the-start-response-callable
Each header_value must not include any control characters, including carriage
returns or linefeeds, either embedded or at
R. David Murray added the comment:
Yeah, only someone who has studied the RFCs would know that detail. I have no
idea whether or not any email clients/processors actually *use* that
distinction for anything, and I doubt there are very many humans who do :).
--
Demian Brecht added the comment:
Contributors may need to update their repos before this step. It would be
good to add a note about git pull --rebase.
Working through this flow actually exposed a blocking issue as far as this
guide goes. As I understand it, because Mercurial sends hashes of
Antoine Pitrou added the comment:
Le 09/12/2014 17:36, Demian Brecht a écrit :
One option would be to increase LimitRequestFieldSize in Apache, but
that really is only a stopgap solution as that limit will be hit again
as one's local repo grows over time. It really would be nice to allow
read
Serhiy Storchaka added the comment:
I afraid this will silence unexpected errors.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23016
___
___
Demian Brecht added the comment:
One option would be to increase LimitRequestFieldSize in Apache, but that
really is only a stopgap solution as that limit will be hit again as one's
local repo grows over time. It really would be nice to allow read only access
via SSH, which isn't affected by
Alexander Belopolsky added the comment:
v3 looks good to me. BTW, I knew that the sign of TZ was significant, but
would have to look up the RFC to recall what the significance was. Thanks,
David, for the explanation.
--
___
Python tracker
Demian Brecht added the comment:
Did you actually hit this issue with hg.python.org?
Yes I did, with only one additional head:
https://gist.github.com/demianbrecht/f525cceda8a0c99794ae. This would also lead
me to believe that the public at large will also start hitting this with the
Amaury Forgeot d'Arc added the comment:
Oh, has this ABI compatibility requirement changed from the 2.x series?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23020
___
Benjamin Peterson added the comment:
We never had compatibility between 2.N and 2.(N + 1) either.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23020
___
Changes by Pablo Aguiar scorp...@gmail.com:
--
nosy: +scorphus
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14787
___
___
Python-bugs-list
Guido van Rossum added the comment:
The example code is a perversion and should not be encouraged.
--
resolution: - rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18305
Amaury Forgeot d'Arc added the comment:
I would not mind the change, but I've always thought the opposite (except on
Windows, where the string Python27.dll is stored in the .pyd)
There are traces of this binary compatibility still today in the 3.4 headers:
PJ Eby added the comment:
The fix for the server looks ok, but the validation and tests must not
be changed, since they void spec compatibility and aren't a bug fix
(and so must not be added to 2.7.) Indeed, if the validation library
*doesn't* fail on CRLF, then *that* would be a bug, since
Barry A. Warsaw added the comment:
Targetting to 3.5 and nosying myself. It would be nice if it were possible to
suppress the help of an entire subparser, but I took a quick look at the code
and it seems tricky.
--
nosy: +barry
versions: +Python 3.5 -Python 2.7
Valerie Lambert added the comment:
Fixed the typo and reuploaded. Thanks for spotting that!
--
Added file: http://bugs.python.org/file37403/build_ext_v2.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1703178
Changes by Berker Peksag berker.pek...@gmail.com:
--
stage: patch review - commit review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1703178
___
Changes by Terry J. Reedy tjre...@udel.edu:
--
type: crash - behavior
versions: +Python 3.5 -Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13153
___
Nick Coghlan added the comment:
OK, that sounds good to me, then. From a compatibility perspective, a
porting note for 3.5 should cover it.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23014
Roundup Robot added the comment:
New changeset bd14c4e5ef00 by Berker Peksag in branch '3.4':
Issue #12602: Add missing cross-references to runpy and using/cmdline docs.
https://hg.python.org/cpython/rev/bd14c4e5ef00
New changeset 3a648b3d1694 by Berker Peksag in branch 'default':
Issue #12602:
Roundup Robot added the comment:
New changeset 078dbecf2e2c by Berker Peksag in branch '2.7':
Issue #12602: Add missing cross-references to runpy and using/cmdline docs.
https://hg.python.org/cpython/rev/078dbecf2e2c
--
___
Python tracker
Berker Peksag added the comment:
Thanks for the patch, Éric.
--
assignee: eric.araujo - berker.peksag
nosy: +berker.peksag
resolution: - fixed
stage: commit review - resolved
status: open - closed
type: behavior - enhancement
___
Python tracker
Berker Peksag added the comment:
Updated Serhiy's patch.
--
nosy: +berker.peksag
Added file: http://bugs.python.org/file37404/issue22823-mock.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22823
Changes by Antoine Pitrou pit...@free.fr:
--
nosy: +lemburg, loewis
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23020
___
___
Python-bugs-list
Roundup Robot added the comment:
New changeset 8c337b4a8811 by Berker Peksag in branch 'default':
Issue #17554: Print fetching url ... messages only in verbose mode.
https://hg.python.org/cpython/rev/8c337b4a8811
--
nosy: +python-dev
___
Python
Roundup Robot added the comment:
New changeset 50517a4d7cce by Berker Peksag in branch '3.4':
Issue #21775: shutil.copytree(): fix crash when copying to VFAT
https://hg.python.org/cpython/rev/50517a4d7cce
New changeset 7d5754af95a9 by Berker Peksag in branch 'default':
Issue #21775:
Changes by Yury Selivanov yseliva...@gmail.com:
--
versions: -Python 3.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19903
___
___
Berker Peksag added the comment:
Committed the patch with a NEWS entry. Thanks Greg.
(You can send your SSH key to hgaccou...@python.org. See also
https://docs.python.org/devguide/coredev.html#ssh)
--
nosy: +berker.peksag
resolution: - fixed
stage: commit review - resolved
status:
Steve Dower added the comment:
Rebased and updated NEWS, so here's a complete patch (and it's all in the
latest change in https://hg.python.org/sandbox/steve.dower#Projects)
--
Added file: http://bugs.python.org/file37405/round7complete.diff
___
Eric Snow added the comment:
FYI, you probably don't want to be patching out sys.modules. It isn't
guaranteed that doing so will have the expected effect on import semantics.
--
nosy: +eric.snow
___
Python tracker rep...@bugs.python.org
Eric Snow added the comment:
I haven't had time for a while to do much work on this. At the last posting
this patch was basically done. I'm sure it no longer applies cleanly. The
biggest obstacle to wrapping this issue up is the size of the patch. It's hard
to get a thorough review
Arfrever Frehtes Taifersar Arahesis added the comment:
Extensions need not to be rebuilt only when using stable ABI:
https://www.python.org/dev/peps/pep-0384/
But mytest.c fails to build with -DPy_LIMITED_API so it uses features from
outside of stable ABI and must be rebuilt.
--
nosy:
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16991
___
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17554
___
Björn Karge added the comment:
I strongly disagree. The constants are just useless as they are (so this bug
can hardly be considered a feature). The behaviour is not matching the 2.7
docs, so fixing it certainly won't be adding a new feature, and the python 3
behaviour can easily be preserved
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23014
___
79 matches
Mail list logo
