STINNER Victor added the comment:
Is it safe to assume PyUnicode_AsUTF8() is null-terminated?
Yes, Python ensures that the string is null terminated.
(like PyBytes_AS_STRING() is)
Yes, PyBytes_AS_STRING() also ends with a null byte.
By the way, Unicode strings internally ends with a null
New submission from Kevin Benton:
If one of the mock.patch methods is used with autospec=True on a staticmethod
in an object, the mock library determines that it is not callable by checking
for the __call__ attribute. This results in a NonCallableMagicMock being
returned which of course dies
Kimmo Parviainen-Jalanko added the comment:
Seems to happen on FreeBSD 10.1 as well with 3.4.2
--
nosy: +Kimmo.Parviainen-Jalanko
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23057
___
STINNER Victor added the comment:
Seems to happen on FreeBSD 10.1 as well with 3.4.2
FreeBSD uses a completly different implementation. Please open a new issue,
describe your problem and write a script reproducing your issue.
--
___
Python tracker
Serhiy Storchaka added the comment:
LGTM.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23071
___
___
Python-bugs-list mailing list
Serhiy Storchaka added the comment:
I think breaking the compatibility should be discussed on Python-Dev. Similar
issue (and even worse) is issue8934.
--
nosy: +serhiy.storchaka
___
Python tracker rep...@bugs.python.org
Marc-Andre Lemburg added the comment:
+1
--
nosy: +lemburg
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23071
___
___
Python-bugs-list mailing
Björn Dahlgren added the comment:
I ran across this bug too. Applying Eduardo's patch got my package
working under Py 3.4
--
nosy: +Björn.Dahlgren
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21697
New submission from Chris Jerdonek:
The documentation for os.path.normcase(path) is currently confusing or
self-contradictory.
Currently, it reads--
Normalize the case of a pathname. On Unix and Mac OS X, this returns the path
unchanged; on case-insensitive filesystems, it converts the path
Serhiy Storchaka added the comment:
s/on case-insensitive filesystems/on Windows/ ?
--
nosy: +serhiy.storchaka
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23079
___
Serhiy Storchaka added the comment:
... and OS/2 (in 2.7).
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23079
___
___
Python-bugs-list mailing
New submission from Antony Lee:
This patch makes BoundArguments.arguments an unordered dict. As discussed on
python-ideas, the rationale for this is
1. The current ordering in ba.arguments is the one of the parameters in the
signature (which is already available via the ba.signature
New submission from Lars Buitinck:
PySequence_List has accepted iterables since changeset 6c82277e77f3 of May 1,
2001 (NEEDS DOC CHANGES :), but its documentation still only speaks of
sequences. I suggest that it is changed to promise to handle arbitrary
iterables, just like PySequence_Tuple.
New submission from Chris Jerdonek:
pathlib's relative_to(other) can give a confusing message when other is
os.curdir.
For example--
Python 3.4.2 (default, Nov 12 2014, 18:23:59)
[GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.54)] on darwin
Type help, copyright, credits or
Chris Jerdonek added the comment:
By the way, here is another (less) confusing error message:
Path(foo).relative_to(fo)
Traceback (most recent call last):
File stdin, line 1, in module
File
Chris Jerdonek added the comment:
Was this also fixed for Mac OS X? Mac OS X is also case-insensitive by
default, and on Python 3.4.2 I'm getting:
Path(Foo).relative_to(foo)
Traceback (most recent call last):
File stdin, line 1, in module
File
R. David Murray added the comment:
Or would s/case-insensitive/not case-preserving/ be more accurate? (Well,
you'd probably rewrite the sentence to eliminate the 'not').
--
nosy: +r.david.murray
___
Python tracker rep...@bugs.python.org
R. David Murray added the comment:
A backward compatibility break would certainly need to be discussed, IMO.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21071
___
Serhiy Storchaka added the comment:
Or would s/case-insensitive/not case-preserving/ be more accurate? (Well,
you'd probably rewrite the sentence to eliminate the 'not').
This would not be more accurate because behavior depends from OS, not from file
system. On Unix/Linux your can mount
Antoine Pitrou added the comment:
pathlib is case-sensitive under OS X (under any non-Windows platform actually).
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19918
___
New submission from Polux Moon:
when using a bool as parameter implementation (2.7) behave like:
sys.exit(True) = sys.exit(1)
sys.exit(False) = sys.exit(0)
so the bool indicate if the termination is abnormal
following the doc it should be equivalent to sys.exit(1) in all cases
if we assume the
R. David Murray added the comment:
issubclass(bool, int)
True
True == 1
True
[41846 refs]
False == 0
True
This is fundamental to Python, so it is not obvious that it is a good idea to
mention bool explicitly in the sys.exit docs. Perhaps we could change it to
say int (or an int subclass
Eric V. Smith added the comment:
I'm not sure this should be documented. It follows from int and bool
equivalence. Plus, I consider it an anti-pattern.
We don't want to document everywhere you can pass a bool where an int is called
for. That's thousands of places.
--
nosy:
R. David Murray added the comment:
Hmm. Good point about the anti-pattern. I agree that it is probably best to
leave the docs as they are.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23083
Changes by Serhiy Storchaka storch...@gmail.com:
--
keywords: +needs review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19104
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
keywords: +needs review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22896
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
keywords: +needs review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23001
___
___
Changes by Piotr Dobrogost p...@bugs.python.dobrogost.net:
--
nosy: +piotr.dobrogost
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6792
___
___
Serhiy Storchaka added the comment:
Here is sample patch which adds two restrictions. Default reduce method for
protocol = 2 will forbid pickling objects:
1) When tp_new == NULL.
2) Builtins without any of pickle-related methods: __getnewargs_ex__,
__getnewargs__ or __getstate__.
Are there
Raymond Hettinger added the comment:
I agree that the docs are best as-is.
--
nosy: +rhettinger
resolution: - rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23083
Changes by Serhiy Storchaka storch...@gmail.com:
--
keywords: +patch
Added file: http://bugs.python.org/file37494/pickle_restrictions.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22995
Changes by Serhiy Storchaka storch...@gmail.com:
--
keywords: +needs review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22113
___
___
New submission from mdcb:
nanosecond support has been discussed at length on python-dev and issue 15443.
POSIX.1b defines a struct timespec that is commonly used in C, and seems a good
candidate to add core nanosecond support. kernel's time-related structs
typically end up in the time module.
Changes by mdcb mdcb...@gmail.com:
--
hgrepos: -289
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23084
___
___
Python-bugs-list mailing list
Changes by Ethan Furman et...@stoneleaf.us:
--
nosy: +belopolsky, ethan.furman, lemburg
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23084
___
New submission from Gustavo Temple:
Link to the file:
https://github.com/gustavotemple/cpython/pull/2.diff
Link to the changes:
https://github.com/gustavotemple/cpython/pull/2/commits
--
components: ctypes
files: libffi.patch
keywords: patch
messages: 232890
nosy: doko, gustavotemple,
Matthias Klose added the comment:
some issues:
- the local change for Windows still needs upstream forwarding.
Steve, any progress on this?
- the libffi.diff is not updated (including Steve's changes)
- this should be applied to 2.7 as well.
--
nosy: +steve.dower, tim.golden,
Changes by Gustavo Temple gustavo.pedr...@eldorado.org.br:
--
title: update internal libffi copy to 3.1 - update internal libffi copy to
3.2.1
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23085
Changes by Eric V. Smith e...@trueblade.com:
--
stage: - resolved
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23083
___
___
Python-bugs-list
Alexander Belopolsky added the comment:
See also discussion in #9079, #14127 and #14180. At some point there was some
resistance to use capsule mechanism to share code within stdlib and the
functions that were shared between time and datetime modules were moved to the
core.
I am -1 on
Gustavo Temple added the comment:
@doko, sorry, but what are the Steve's changes? The issue #22733?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23085
___
Ethan Furman added the comment:
I haven't reviewed the patch yet, but I believe the intent is not for better
sleep support, but simply to be able to create and record time data which
contains nano-seconds.
python-dev discussion here:
Alexander Belopolsky added the comment:
.. the intent is not for better sleep support, but simply
to be able to create and record time data which contains nano-seconds.
Can you describe a specific use-case? What's the advantage of the proposed
time.struct_timespec over say
timespec =
Alexander Belopolsky added the comment:
time() could be used to produce them
How?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23084
___
___
Steve Dower added the comment:
I think Matthias is referring to #20160, but as far as I could tell libffi is
multiple versions ahead of the version in Python and already has the fixes. I
was told to wait for it to be submitted/accepted upstream, so I've been waiting
:)
--
Steve Dower added the comment:
This was fixed with #22919.
--
resolution: - fixed
stage: - resolved
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21236
___
Matthias Klose added the comment:
you should actively drive upstream integration, and ping patches if they are
not addressed.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23085
___
Steve Dower added the comment:
As I mentioned on the other post, libffi's current version bears no relation to
what we have in CPython, so the patches don't apply. I'm not planning on
rewriting CPython patches so that they will apply to libffi, nor do I intend to
replace our current version
Changes by Gustavo Temple gustavo.pedr...@eldorado.org.br:
Added file: http://bugs.python.org/file37497/atomicv3.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22038
___
Gustavo Temple added the comment:
@haypo, done: atomicv3.patch
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22038
___
___
Python-bugs-list
Changes by Gustavo Temple gustavo.pedr...@eldorado.org.br:
Removed file: http://bugs.python.org/file37497/atomicv3.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22038
___
Changes by Gustavo Temple gustavo.pedr...@eldorado.org.br:
Added file: http://bugs.python.org/file37498/atomicv3.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22038
___
Changes by Gustavo Temple gustavo.pedr...@eldorado.org.br:
Removed file: http://bugs.python.org/file37498/atomicv3.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22038
___
Changes by Gustavo Temple gustavo.pedr...@eldorado.org.br:
Added file: http://bugs.python.org/file37499/atomicv3.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22038
___
Changes by Gustavo Temple gustavo.pedr...@eldorado.org.br:
Added file: http://bugs.python.org/file37500/atomicv3.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22038
___
Changes by Gustavo Temple gustavo.pedr...@eldorado.org.br:
Removed file: http://bugs.python.org/file37499/atomicv3.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22038
___
STINNER Victor added the comment:
See the issue #22117 which basically implement the PEP 410, but only for
private C API. The idea is to avoid loss of precision caused by the float type
when it is possible. For example, it would be possible for
datetime.datetime.now() to avoid the float time.
Changes by mike bayer mike...@zzzcomputing.com:
--
nosy: +zzzeek
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22956
___
___
Python-bugs-list
Marc-Andre Lemburg added the comment:
Will this also fix http://bugs.python.org/issue23042 ?
--
nosy: +lemburg
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23085
___
New submission from Raymond Hettinger:
Currently, the Sequence ABC doesn't support start and stop arguments for the
index() method which limits its usefulness in doing repeated searches
(iterating over a target value) and which limits it substitutablity for various
concrete sequences such as
Alexander Belopolsky added the comment:
it would be possible for datetime.datetime.now()
to avoid the float time.
C implementation of datetime.now() does not rely on float time, so this is only
an issue for the Python implementation.
Moreover, as long as datetime keeps its microsecond
STINNER Victor added the comment:
C implementation of datetime.now() does not rely on float time, so this is
only an issue for the Python implementation.
Ah yes, but there is another technical issue that I'm trying to address in the
issue #22117: datetime.datetime.now() is implemented with
New submission from Keith Chewning:
If I %paste this code into an ipython shell the test passes. If this is saved
to a file DictTest.py and run with ./DictTest.py -m the test fails. with the
error
name 'keys' is not defined
If the variable keys is made global, as is suggested in the comment,
Alexander Belopolsky added the comment:
Would anyone object if I rename this issue to Expose C struct timespec in time
module? The current title is way too broad.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23084
Terry J. Reedy added the comment:
I should note that in msg225543 of #22179, I verified that there is a problem
in Replace for highlighting found text within quotes, as well as in keywords,
until the dialog is closed. On the other hand, the same text is hihglighted in
identifiers, plain
Ethan Furman added the comment:
Just keep the word nanasecond in there somewhere, as that is the motivating
purpose behind the patch.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23084
Changes by R. David Murray rdmur...@bitdance.com:
--
nosy: +r.david.murray
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23087
___
___
Changes by Alexander Belopolsky alexander.belopol...@gmail.com:
--
title: nanosecond support - Expose C struct timespec (nanosecond resolution)
in time module
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23084
Alexander Belopolsky added the comment:
I would say that rejection note for PEP 410 [1] and the implementation of
st_[amc]time_ns fields in os.stats() have established a de-facto standard for
representing nanosecond resolution timestamps in Python.
I think this proposal should be rejected.
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23001
___
___
Python-bugs-list
Ethan Furman added the comment:
If I am reading data from an external device that has nanosecond resolution,
how would I create such a time stamp in Python right now?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23084
mdcb added the comment:
I'm going to be my own devil's advocate:
PyLong_FromLong
...
Thanks for all the links, I hadn't realized there was so much background to the
issue, there is some good reading there too.
you've changed the title now, but in fact the intention was the other aspect,
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23084
___
Alexander Belopolsky added the comment:
If I am reading data from an external device that has nanosecond
resolution, how would I create such a time stamp in Python right now?
seconds * 10**9 + nanoseconds (translated to C API if necessary)
--
___
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23042
___
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23085
___
mdcb added the comment:
can we change back the title because in fact, exposing struct timespec wasn't
really the intention (but keep the patch if you want it!)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23084
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23087
___
Alexander Belopolsky added the comment:
but that seems to loose the type information after doing arithmetics
Hear, hear. See #2267. If you find out why Python was designed this way - let
me know.
--
___
Python tracker rep...@bugs.python.org
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22038
___
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22113
___
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22995
___
Changes by Terry J. Reedy tjre...@udel.edu:
--
dependencies: -Idle. Search dialog found text not highlited on Windows
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18590
___
Terry J. Reedy added the comment:
The first # comment above should be On Windows, the selection highlight is
*not* visible while the modal dialog is open. This bug was, in a sense,
introduced by #17511, which kept the dialog open after [Find] is pressed,
instead of closing it immediately.
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19104
___
Alexander Belopolsky added the comment:
can we change back the title because in fact
Please don't. If you would like to discuss general ideas - the right forum
would be the python-ideas mailing list.
We have no shortage of issue numbers: once you have another specific proposal -
feel free
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16349
___
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21071
___
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8934
___
Arfrever Frehtes Taifersar Arahesis added the comment:
list(pathlib.Path().glob())
Traceback (most recent call last):
File stdin, line 1, in module
File /usr/lib64/python3.5/pathlib.py, line 999, in glob
selector = _make_selector(tuple(pattern_parts))
File
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
assignee: - pitrou
nosy: +Arfrever, pitrou
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23082
___
mdcb added the comment:
I'm fine my patch doesn't resolve the nanosecond support, but that doesn't
mean the issue is closed per say.
Ref. to PEP410 rejection and de facto standard seems a bit expeditive.
assuming it worked, this would somewhat be more agreeable ?
class timestamp(int): pass
mdcb added the comment:
firefox did something and changed some fields I did not intend to. I'm trying
to undo that now.
--
resolution: - rejected
status: open - pending
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23084
Alexander Belopolsky added the comment:
nanosecond support [in Python] is a PEP-size topic. As Victor suggested, If
you are motivated enough, you may update the PEP and write a new one. The
tracker does not provide a sufficiently large forum to discuss nanosecond
support in full generality.
Changes by Berker Peksag berker.pek...@gmail.com:
--
nosy: +yselivanov
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23080
___
___
Changes by Berker Peksag berker.pek...@gmail.com:
--
nosy: +berker.peksag, tim.peters
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23081
___
___
Yury Selivanov added the comment:
I'd like to see PEP 468 explicitly rejected or postponed till 3.6 before we
make this change in 3.5.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23080
Martin Panter added the comment:
Here is a patch with a fix and a test
--
keywords: +patch
Added file: http://bugs.python.org/file37501/fail-close.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22350
New submission from Martin Panter:
As discussed in msg232863, and later confirmed in the code
--
assignee: docs@python
components: Documentation
files: utf8-null.patch
keywords: patch
messages: 232925
nosy: docs@python, vadmium
priority: normal
severity: normal
status: open
title:
Terry J. Reedy added the comment:
I am narrowing the scope of this issue to Replace dialogs and widening the
scope to output as well as edit windows. The attached patch solves the issue as
redefined. (It has a temporary hack to pass the unittests.)
For edit windows, the problem is that the
1 - 100 of 104 matches
Mail list logo
