Georg Brandl added the comment:
Well, there's no bug here: it's what you get when you call a library the same
as a builtin :)
--
resolution: -> wont fix
status: open -> closed
___
Python tracker
<http://bugs.py
Georg Brandl added the comment:
-1.
First, I don't think stdlib modules should be forced to use old conventions and
give up on new features just because of backports (the import changes are fine
obviously).
Second, it's putting unreasonable constraints on CPython developers to k
Georg Brandl added the comment:
That would be correct as a handwaving description, but it's wrong as a formal
spec. The "or_expr" already includes the possibility of a tuple; there is no
"exec(" token etc.
--
nosy: +georg.brandl
resolution: -> works f
Georg Brandl added the comment:
As Victor says, I'm not keen on those examples in the stdlib that do this, I'd
rather get rid of all of them.
And yes, doctests are only useful if they are written in the simplest possible
way. Otherwise unittest style tests should be
Georg Brandl added the comment:
Thanks, should be fixed now.
--
nosy: +georg.brandl
___
Python tracker
<http://bugs.python.org/issue19622>
___
___
Python-bug
Georg Brandl added the comment:
``False`` is actually the preferred way, being shorter and easier to read (and
we don't need to link to the documentation for False).
--
nosy: +georg.brandl
___
Python tracker
<http://bugs.python.org/is
Georg Brandl added the comment:
When citing a link, it's customary to give at least a comment *why* you are
citing it.
--
nosy: +georg.brandl
___
Python tracker
<http://bugs.python.org/is
Georg Brandl added the comment:
For a true security fix, the default for check_hostname would have to be True.
However, that will create a lot of backward compatibility problems for
questionable gain.
I think Larry should make an exception for 3.4 and allow this new feature
Georg Brandl added the comment:
Hmm, sucks.
Benjamin, can you come up with a fix? I'll give it a few weeks to wait for
more potential regressions and then do a 3.3.4.
--
___
Python tracker
<http://bugs.python.org/is
Changes by Georg Brandl :
--
nosy: -georg.brandl
versions: -Python 3.3, Python 3.4
___
Python tracker
<http://bugs.python.org/issue19810>
___
___
Python-bug
Georg Brandl added the comment:
Closing for the hopefully final time. Anatoly, if you keep reopening this
ticket you have to expect removal of tracker privileges.
--
nosy: +georg.brandl
resolution: postponed -> rejected
status: open ->
Changes by Georg Brandl :
--
nosy: -georg.brandl
___
Python tracker
<http://bugs.python.org/issue22162>
___
___
Python-bugs-list mailing list
Unsubscribe:
Georg Brandl added the comment:
Looks good except for this one:
-# Remove the 'Current' link, that way we don't accidentally mess
+# Remove the 'Current' link, that way we don't accidentaly mess
--
nosy: +georg.brandl
Changes by Georg Brandl :
--
nosy: -georg.brandl
___
Python tracker
<http://bugs.python.org/issue22034>
___
___
Python-bugs-list mailing list
Unsubscribe:
Georg Brandl added the comment:
Not much more we can do from here.
--
nosy: +georg.brandl
resolution: -> third party
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
Georg Brandl added the comment:
We know, but this will happen to any sites that have content hosted by a CDN
such as Fastly.
In this specific case, you can download the docs or build them yourself for
offline usage. Our Mercurial server hg.python.org is (obviously :) not hosted
on a CDN, so
Georg Brandl added the comment:
Very nice, thanks for the update.
--
___
Python tracker
<http://bugs.python.org/issue4>
___
___
Python-bugs-list mailin
Georg Brandl added the comment:
I agree: The docs for list.sort() do guarantee the stability, so sorted()
should have the same indication.
--
nosy: +georg.brandl
___
Python tracker
<http://bugs.python.org/issue22
Georg Brandl added the comment:
+1
--
nosy: +georg.brandl
versions: -Python 3.1, Python 3.2, Python 3.3
___
Python tracker
<http://bugs.python.org/issue22
Changes by Georg Brandl :
--
status: closed -> open
___
Python tracker
<http://bugs.python.org/issue2771>
___
___
Python-bugs-list mailing list
Unsubscrib
Changes by Georg Brandl :
--
resolution: -> not a bug
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue22414>
___
___
Python-bugs-
Georg Brandl added the comment:
The anchor for dict is on the "standard types" page:
https://docs.python.org/2/library/stdtypes.html#dict
You'll have to use :class: not :func: to get it linked.
--
resolution: -> works for me
stat
Georg Brandl added the comment:
Sorry for the "mismanagement", I probably didn't check again after the final
resolution.
--
nosy: +georg.brandl
___
Python tracker
<http://bugs.pyt
Georg Brandl added the comment:
I have no idea about that code, and I can't reproduce the failure.
(Could the buildbots?)
--
___
Python tracker
<http://bugs.python.org/is
Georg Brandl added the comment:
That is very likely the reason. So far nobody has run the builder with Python 3.
--
___
Python tracker
<http://bugs.python.org/issue22
Georg Brandl added the comment:
Yep.
--
resolution: -> duplicate
status: open -> closed
superseder: -> 3.4.1rc1 test_pydoc fails: pydoc_data.topics.topics values are
type "bytes" not "str"
___
Python tracker
<h
Georg Brandl added the comment:
Should be fixed now. I didn't merge into default since someone (cough) has to
null-merge all the release related stuff first.
--
___
Python tracker
<http://bugs.python.org/is
Georg Brandl added the comment:
Left this open in case you have additional patches coming.
--
nosy: +georg.brandl
___
Python tracker
<http://bugs.python.org/issue22
New submission from Georg Brandl:
This is implicit in the "converts arguments to strings", but people might
reasonably expect that print(x, file=y) is the same as y.write(x) for strings
and bytes. This paragraph makes it clear.
--
files: print_binary.diff
keywords: patc
Georg Brandl added the comment:
These "errors" are all valid markup. They would have been discovered much
earlier had they been errors.
Please consider checking why your Sphinx setup produces the errors, fixing it
and then reverting t
Changes by Georg Brandl :
--
versions: -Python 3.1
___
Python tracker
<http://bugs.python.org/issue16038>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Georg Brandl :
--
versions: -Python 3.1
___
Python tracker
<http://bugs.python.org/issue18747>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Georg Brandl :
--
versions: -Python 3.1
___
Python tracker
<http://bugs.python.org/issue16042>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Georg Brandl :
--
versions: -Python 3.1
___
Python tracker
<http://bugs.python.org/issue16041>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Georg Brandl :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue18709>
___
___
Python-bugs-list mailing list
Unsubscrib
Georg Brandl added the comment:
Since it's been out in 3.2.x for so long, I won't apply this for 3.2 since at
this point a behavior change might do more harm than good.
--
resolution: -> fixed
status: open -> closed
versions: +Python 3.3, Python
Changes by Georg Brandl :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue18747>
___
___
Python-bugs-list
Changes by Georg Brandl :
--
versions: -Python 3.2
___
Python tracker
<http://bugs.python.org/issue16041>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Georg Brandl :
--
versions: -Python 3.2
___
Python tracker
<http://bugs.python.org/issue16042>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Georg Brandl :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue16038>
___
___
Python-bugs-list
Changes by Georg Brandl :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue16037>
___
___
Python-bugs-list
Georg Brandl added the comment:
Note that these methods were already part of Jason's path.py when I imported it
for use by Sphinx.
I think these convenience methods are useful indeed, so if it is fine with your
philosophy for pathlib, I'd be happy to see them there. The
Georg Brandl added the comment:
Benjamin, could you make a patch for 3.2 as well?
--
nosy: +georg.brandl
___
Python tracker
<http://bugs.python.org/issue22
Georg Brandl added the comment:
I wouldn't consider this important enough for 3.2; since it lacks the means to
do the opt-back-in.
--
nosy: +georg.brandl
versions: -Python 3.2
___
Python tracker
<http://bugs.python.org/is
Changes by Georg Brandl :
--
versions: -Python 3.1, Python 3.2
___
Python tracker
<http://bugs.python.org/issue16039>
___
___
Python-bugs-list mailing list
Unsub
Georg Brandl added the comment:
Next try.
--
Added file: http://bugs.python.org/file36761/pathlib_readwrite_v5.patch
___
Python tracker
<http://bugs.python.org/issue20
Georg Brandl added the comment:
Let me check that.
--
___
Python tracker
<http://bugs.python.org/issue16039>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Georg Brandl :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue16039>
___
___
Python-bugs-list
Georg Brandl added the comment:
Looks obvious and is potentially a security fix, so it can/should go in.
Please add a NEWS entry.
--
___
Python tracker
<http://bugs.python.org/issue19
Georg Brandl added the comment:
Serhiy, would you make a patch for 3.2 too?
--
nosy: +georg.brandl
___
Python tracker
<http://bugs.python.org/issue19855>
___
___
Changes by Georg Brandl :
Added file: http://bugs.python.org/file36762/pathlib_readwrite_v6.patch
___
Python tracker
<http://bugs.python.org/issue20218>
___
___
Python-bug
Georg Brandl added the comment:
I agree that the wording can be improved. The term "expression" is used here
loosely, but should be clarified.
"a+b" with numbers a, b must be handled in order to evaluate complex literals
as in "1+1j".
Allowing operator express
Georg Brandl added the comment:
Thanks!
--
___
Python tracker
<http://bugs.python.org/issue19855>
___
___
Python-bugs-list mailing list
Unsubscribe:
Georg Brandl added the comment:
I agree with Ned. 3.2 is not maintained anymore, we only provide security fixes.
(Exceptions prove the rule. One exception I committed today was to stop
test_urllibnet from failing, so that I could better see real failures on the
buildbots
Georg Brandl added the comment:
Attaching proposed doc change.
--
keywords: +patch
Added file: http://bugs.python.org/file36764/ast_literal_eval_clarify.patch
___
Python tracker
<http://bugs.python.org/issue22
Georg Brandl added the comment:
The function is still called literal_eval(), not safe_eval().
I'm not saying a safe eval() isn't useful. But an implementation that is only
partly safe is not going to help anyone.
--
___
Python trac
Georg Brandl added the comment:
These are a bug in Sphinx 1.2.1 and fixed in 1.2.2.
--
nosy: +georg.brandl
resolution: -> third party
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
Georg Brandl added the comment:
Sure, feel free to reword.
An example or two might also be helpful.
--
___
Python tracker
<http://bugs.python.org/issue22
Georg Brandl added the comment:
Looks good.
> sys.stdout, when rebound to a binary mode file
Not sure that is supported in any way :)
--
___
Python tracker
<http://bugs.python.org/issu
Georg Brandl added the comment:
It's not so surprising, since the string before the milliseconds part is a
strftime() result, not a whole number. The decimal point need not necessarily
be used for this.
Just like the rest of the default time format, it is probably best for the
millis
Georg Brandl added the comment:
Committed in 18983332626b.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
Georg Brandl added the comment:
I see test failures on Windows:
http://buildbot.python.org/all/builders/AMD64%20Windows7%20SP1%20custom/builds/62/steps/test/logs/stdio
http://buildbot.python.org/all/builders/x86%20Windows7%20custom/builds/52/steps/test/logs/stdio
Do the tests need changing
Changes by Georg Brandl :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue19855>
___
___
Python-bugs-list mailing list
Unsubscrib
Georg Brandl added the comment:
> you now do need
You always did :)
However, it should not be a problem to make the extensions 2.x and 3.x
compatible in both branches.
--
___
Python tracker
<http://bugs.python.org/issu
Georg Brandl added the comment:
LGTM.
--
nosy: +georg.brandl
___
Python tracker
<http://bugs.python.org/issue19342>
___
___
Python-bugs-list mailing list
Unsub
Georg Brandl added the comment:
I'm attaching a patch that works without changing the recursion limit, and adds
some tests for pathological cases.
Instead, PyErr_GivenExceptionMatches is changed so that if an exception was
previously set, it is replaced by an exception
Georg Brandl added the comment:
New version including (I think) correct refcount handling.
--
Added file:
http://bugs.python.org/file36777/exception_proper_subclass_matching_v2.patch
___
Python tracker
<http://bugs.python.org/issue12
Georg Brandl added the comment:
Clarifying some comments in this one.
--
Added file:
http://bugs.python.org/file36778/exception_proper_subclass_matching_v3.patch
___
Python tracker
<http://bugs.python.org/issue12
Changes by Georg Brandl :
Removed file:
http://bugs.python.org/file36776/exception_proper_subclass_matching.patch
___
Python tracker
<http://bugs.python.org/issue12
Georg Brandl added the comment:
This needs a lot more information, such as the full config.log and output of
"make".
Kernel 2.6.18 is also quite old, so if there is no feedback if this is still an
issue I'd suggest to close the report.
--
nosy: +georg.brandl
status:
Changes by Georg Brandl :
--
status: pending -> open
title: getaddrinfo() bug -> configure and compile problems with older CentOS
releases
___
Python tracker
<http://bugs.python.org/i
Georg Brandl added the comment:
While everybody is throwing ideas around: what about the opposite?
If extracting bit ranges from bitfields is common enough to warrant this
addition, updating bitfields with a bit range is probably just as common.
This'd need something like
i.with_bits(
Georg Brandl added the comment:
This is why I proposed it (and also because I had to write that quite a few
times already). Efficient maybe, but very hard to get right on the first try :)
--
___
Python tracker
<http://bugs.python.org/issue19
Georg Brandl added the comment:
Agreed.
Since type has __subclasscheck__ (why I don't know) this might result in a
slowdown since all checks have to go through calling it in PyObject_IsSubclass.
Just noticed that given_exception_matches_inner can be simplified a bit since
PyObject_IsSub
Georg Brandl added the comment:
Quick microbenchmark:
try:
{}["a"]
except KeyError:
pass
original tip: 1.35 usec
with patch v3: 1.55 usec
so it's about 15% slowdown for catching a simple exceptio
Georg Brandl added the comment:
OK, with these two patches (speedup and v4) I can't see a significant slowdown
anymore.
--
Added file:
http://bugs.python.org/file36779/pyobject_issubclass_isinstance_speedup.patch
___
Python tracker
Changes by Georg Brandl :
Added file:
http://bugs.python.org/file36780/exception_proper_subclass_matching_v4.patch
___
Python tracker
<http://bugs.python.org/issue12
New submission from Georg Brandl:
With the introduction of ABCs, PyObject_IsInstance (and for this issue,
everything is also valid for PyObject_IsSubclass) has to check for a type's
__instancecheck__ before falling back to the built-in behavior.
However, the "type&qu
Georg Brandl added the comment:
IsSubclass speedup patch now tracked in #22540.
--
dependencies: +speed up isinstance and issubclass for the usual cases
___
Python tracker
<http://bugs.python.org/issue12
Georg Brandl added the comment:
Addressing review comments.
--
Added file:
http://bugs.python.org/file36789/pyobject_issubclass_isinstance_speedup_v2.patch
___
Python tracker
<http://bugs.python.org/issue22
Georg Brandl added the comment:
Thanks for fixing! I did run "make test" locally, but that did not produce the
failure.
--
___
Python tracker
<http://bugs.python.o
Georg Brandl added the comment:
I'm wondering what "regs" is supposed to stand for. It might be for "regions",
but that term is used nowhere else. It should really be named "spans" to be
consistent.
--
nosy: +georg.brandl
___
Changes by Georg Brandl :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue22540>
___
___
Python-bugs-list
Georg Brandl added the comment:
Hi Eric,
this paragraph is about slices, where you *can* do
>>> word[0:6]
'Python'
As such, the paragraph is correct.
--
nosy: +georg.brandl
resolution: -> not a bug
status: open -> closed
Georg Brandl added the comment:
IOW: it was already intentionally undocumented back then, and only added for
compatibility reasons.
Probably should be deprecated and removed at some point.
--
resolution: -> wont fix
status: open ->
Georg Brandl added the comment:
No response, closing.
--
nosy: +georg.brandl
resolution: -> out of date
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
Georg Brandl added the comment:
Nobody doubts that pinging old issues helps getting some of them closed. But
messages like msg228480 sound a bit pretentious, that's what Antoine is
referring to.
--
nosy: +georg.brandl
___
Python tracker
Georg Brandl added the comment:
> As mentioned before, many packages can not handle paths with spaces.
This is "common knowledge", yet may not be true anymore. See this recent
python-dev thread:
https://mail.python.org/pipermail/python-dev/2014-Septembe
Georg Brandl added the comment:
Not a Python issue.
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue20997>
___
___
Python-bugs-lis
Georg Brandl added the comment:
This is indeed intended. I'll update the docs.
--
nosy: +georg.brandl
resolution: -> not a bug
status: open -> closed
___
Python tracker
<http://bugs.python.
Georg Brandl added the comment:
I don't think this can go somewhere useful.
--
resolution: -> wont fix
status: open -> closed
___
Python tracker
<http://bugs.python
Georg Brandl added the comment:
asdl.py is fixed to work with 2.7 as of 3b2af26f4638.
--
nosy: +georg.brandl
___
Python tracker
<http://bugs.python.org/issue21
Georg Brandl added the comment:
A more complete patch that also fixes up pyexpat's frame trickery is tracked in
#22462.
--
nosy: +georg.brandl
resolution: -> duplicate
status: open -> closed
superseder: -> Modules/pyexpat.c vi
Georg Brandl added the comment:
Not sure how this can violate PEP 384, as it doesn't make it mandatory for
builtin extensions to use the stable ABI.
The other concerns seem valid, although I don't like how the patch includes an
unrelated change to ctypes.
--
nosy: +ge
Georg Brandl added the comment:
I seem to recall that this was rejected into the realm of linters in a
python-dev discussion.
If there is a chance of false positives, having Python emit the warning would
be annoying because there is no convenient way of telling it to shut up about
it. At
Georg Brandl added the comment:
Please open a new issue for those.
--
nosy: +georg.brandl
___
Python tracker
<http://bugs.python.org/issue16518>
___
___
Python-bug
Georg Brandl added the comment:
I agree, closing.
--
nosy: +georg.brandl
resolution: -> wont fix
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
Georg Brandl added the comment:
pydoc.gui() no longer exists in supported versions.
--
nosy: +georg.brandl
resolution: -> out of date
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
Changes by Georg Brandl :
--
resolution: -> fixed
status: open -> pending
___
Python tracker
<http://bugs.python.org/issue21072>
___
___
Python-bugs-list
Georg Brandl added the comment:
Since we're unlikely to ever change all the places, I'd say it's better to be
consistent. I'd rather write str(path) all over the place than having to look
up in the docs each time if that specific API happens to support passing Paths
3601 - 3700 of 5257 matches
Mail list logo
