George King added the comment:
Edit: `chr(0xff)`
--
___
Python tracker
<https://bugs.python.org/issue45904>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from George King :
Using macOS 11.6 Terminal.app with Python 3.10.0 installed directly from
python.org.
I open the REPL. If I enter `char(0xff)` I get back 'ΓΏ' as expected (U00FF
LATIN SMALL LETTER Y WITH DIAERESIS).
However, If I copy this character with surrounding quotes
George King added the comment:
I should also mention that my reading was not exhaustive, so there may be other
docs that need updating as well.
--
___
Python tracker
<https://bugs.python.org/issue44
New submission from George King :
`dis.findlinestarts()` has been changed to use the no `co_lines()` function.
(Blame indicates commit 877df851c3e by Mark Shannon.) However the docs
currently state that it uses the older `co_firstlineno` and `co_lnotab`:
https://docs.python.org/3.10/library
George King added the comment:
I think we should change the documentation to expand the parenthetical "
(unless SystemExit is raised)" to a complete explanation of that special case.
--
___
Python tracker
<https://bugs.python.o
New submission from George King :
I was browsing the Blake2b module implementation in master and noticed two
subtle issues in blake2b_impl.c. There are two places where the GIL gets
released; both of them appear flawed.
py_blake2b_new_impl, line 221. The ALLOW_THREADS block fails to acquire
George King added the comment:
I agree that regardless of the underlying issue, the docs should match the
behavior. Additionally, I hope the docs will note the exact release at which
the behavior changed.
@serhiy-storchaka do you have any opinion on this? I took a brief look at your
commit
George King added the comment:
OK, thanks. I agree that this is best pursued with the developers of the
relevant modules. I appreciate your quick and detailed responses!
--
___
Python tracker
<https://bugs.python.org/issue33
George King added the comment:
Thanks Barry. My question then is, what relationship does cpython have with
pip, setuptools, distutils and pkg_resources? Since pip comes bundled with
Python now it seems a little bit closer than "3rd party&quo
New submission from George King :
On my newish macOS laptop using Python 3.6 or 3.7, a no-op script takes 3 times
as long to invoke using the entry_points machinery as it does to invoke
directly. Here are some exemplary times (best times after several tries).
$ time python3.6 entrypoint.py
Change by George King <george.w.k...@gmail.com>:
--
keywords: +patch
pull_requests: +4017
stage: -> patch review
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pyt
Change by George King <george.w.k...@gmail.com>:
--
pull_requests: +4016
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue31681>
___
George King <george.w.k...@gmail.com> added the comment:
Nick's implementation of f_trace_lines/f_trace_opcodes serves the same purpose
as my proposal, and is a simpler solution so I'm abandoning this patch and
working with that feature instead.
--
stage: test needed ->
George King <george.w.k...@gmail.com> added the comment:
The feature was was implemented in bpo-31344. See bpo-29400 for my parallel
effort, which has been abandoned.
--
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
New submission from George King <george.w.k...@gmail.com>:
This patch moves the new opcode tracing added in commit 5a85167 to happen after
frame->f_lineno is updated. With this patch, when both f_trace_lines and
f_trace_opcodes are enabled the trace function will see the same li
Changes by George King <george.w.k...@gmail.com>:
--
pull_requests: +3278
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue29400>
___
George King added the comment:
Attached updated demo script.
--
Added file: http://bugs.python.org/file47107/settracestate-demo.py
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Changes by George King <george.w.k...@gmail.com>:
--
pull_requests: +3277
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue24900>
___
George King added the comment:
(Also I did prototype instruction filtering but it had mild performance
implications when tracing so I have shelved it for the moment.)
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
George King added the comment:
I've updated the patch and I think it's ready for a more serious review. A few
notes:
* settracestate now takes a flag `trace_instructions`. This describes slightly
better the behavior, which is that line events take precedence over
instructions.
* the old
George King added the comment:
After reviewing the thread, I'm reminded that the main design problem concerns
preserving behavior of this idiom:
"old=sys.gettrace(); ...; sys.settrace(old)"
If we add more state, i.e. the `trace_instructions` bool, then the above idiom
no longer
George King added the comment:
@matrixise, I'm the author of the alternative in issue29400, and I'm finally
finding the time to get back into it. I'm going to make a push this week to
clean it up; your feedback would be much appreciated!
--
nosy: +gwk
George King added the comment:
I think it is a mistake not to support None values. Please consider:
The existing message clearly suggests that the intent is to support the same
set of values as the start/stop parameters of the slice type. str, bytes, and
bytearray all support None for `index
Changes by George King <george.w.k...@gmail.com>:
--
type: -> enhancement
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue29935>
___
_
New submission from George King:
As of python3.6, passing None to the start/end parameters of `list.index` and
`tuple.index` raises the following exception:
"slice indices must be integers or None or have an __index__ method"
This suggests that the intent is to support None as a v
George King added the comment:
I'm not sure exactly, but the way I see it (for code coverage), we want to
trace transitions between basic blocks. So I would define it as: each entry
into a BB is traced, with a tuple of (previous_offset, current_offset). This
way when a function call starts
George King added the comment:
Attached is a new patch, which does not settrace/gettrace and instead offers
new settraceinst/gettraceinst per Victor's recommendation.
I did not implement the proposed behavior of raising an exception if the old
APIs are used when the inst_tracing flag is set
George King added the comment:
Thanks to both of you for your feedback. I will take a stab at updating the
patch with Victor's suggestions as soon as I can.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
George King added the comment:
Attached is a demo of using the feature as a fancy replacement for __ltrace__.
It demonstrates using a closure for the local trace function to track the
previous offset, and prints the offset transitions as src -> dst pairs. This
helped me learn a lot about
George King added the comment:
Xavier, this is a misunderstanding; sorry for not being more clear. When I said
"remove the `else`", I was proposing this:
+ if (tstate->inst_tracing) {
+ result = call_trace(func, obj, tstate, frame, PyTrace_INSTRUCTION, Py_None);
+ }
Line-ori
George King added the comment:
Here is the patch from git; if you need a patch for hg I can work on that
tomorrow!
--
keywords: +patch
Added file: http://bugs.python.org/file46475/inst-tracing.diff
___
Python tracker <rep...@bugs.python.org>
New submission from George King:
I have recently put some effort into developing a code coverage tool that shows
correct results for intraline branches. In order to get intraline trace data, I
patched CPython, adding an optional "trace instructions" flag to sys.settrace.
The patch
George King added the comment:
I reinstalled the command line tools by downloading from
developer.apple.com/download/more and the problem went away. No idea how they
broke; I had previously installed the same version. In any case, sorry for the
noise
George King added the comment:
This is using the latest apple toolchain on latest macOS 10.12.2:
$ gcc --version
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr
--with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 8.0.0 (clang-800.0.42.1)
Target: x86_64
George King added the comment:
Still seeing this problem. Here was my exact process:
$ git clone g...@github.com:python/cpython.git
$ cd cpython
$ git checkout 2.7
$ mkdir build
$ cd build
$ ../configure
$ make
In file included from ../Python/random.c:7:
/usr/include/sys/random.h:37:32: error
George King added the comment:
(I meant the github mirror: github.com/python/cpython)
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
George King added the comment:
I am encountering this problem on macOS 10.12.2, with Xcode 8.2.1 (latest).
I have tried building from the following cpython branches today (using the
github fork):
2.7: 13a39142c047
In file included from ../../Python/random.c:7:
/usr/include/sys/random.h:37:32
George King added the comment:
The documentation for atexit.register clearly states that a SystemExit raised
inside of the registered function is a special case:
'''
If an exception is raised during execution of the exit handlers, a traceback is
printed (unless SystemExit is raised
New submission from George King:
I can crash python2.7.5 python3.3.2 from the REPL consistently:
$ python3
Python 3.3.2 (v3.3.2:d047928ae3f6, May 13 2013, 13:52:24)
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin
Type help, copyright, credits or license for more information.
s = '\\t
George King added the comment:
actually, the second line of any interactive session is segfaulting; my
installation must be corrupted.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19366
George King added the comment:
this is probably due to system upgrade from OS X 10.8 to 10.9 (mavericks)
yesterday.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19366
George King added the comment:
thank you. i worked around this by building python3 from source, with gnu
readline libs i had previously compiled (those did not require a rebuild on osx
10.9).
--
___
Python tracker rep...@bugs.python.org
http
New submission from George King gk...@arboreality.net:
My builds from trunk fail to open a number of files greater than the
default 2660, even when I increase the limit using:
resource.setrlimit(resource.RLIMIT_NOFILE, (test_limit, -1))
Attached is a script that doubles the default limit
43 matches
Mail list logo
