Changes by Xavier de Gaye :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Xavier de Gaye added the comment:
Issue 27472 adds test.support.unix_shell as the path to the default shell.
--
___
Python tracker
<http://bugs.python.org/issue16
Xavier de Gaye added the comment:
Yes, issue 27027 adds test.support.is_android and there is no need now to wait
for issue 16353. Thanks David for reminding me, I have just added a
cross-reference to issue 16353.
--
___
Python tracker
<h
Xavier de Gaye added the comment:
The attached patch ignores the following test modules listed in msg266084:
Lib/distutils/tests/test_build_scripts.py|68 col 31| ("#!/bin/sh\n"
Lib/distutils/tests/test_install_scripts.py|57 col 38| write_script("shell.sh",
("#!/
Xavier de Gaye added the comment:
> the underlying problem is that pgen gets built in cases where it shouldn't
This statement does not take into account the following note of your initial
post: "note that the same $(CFLAGS) needs to be added to the rule for
$(BUILDPYTHON) if
Xavier de Gaye added the comment:
I confirm that, on 3.6 and after the changesets that fixed issue 22359, pgen is
always cross-compiled whatever the timestamps and that pgen is not run on a
cross-build for Android. So I think it should work as well now for Trevor with
v2.7.12
Xavier de Gaye added the comment:
This patch follows the first mechanism listed by Martin. The change in
configure.ac fixes the problem described by Victor, it does not generate an
empty Objects/typeslots.inc file when python is not found that would cause the
cryptic " : invalid slot o
Xavier de Gaye added the comment:
Forgot to say that with the patch and no python in $PATH, the following error
message is output:
$ touch Include/typeslots.h
$ make
Cannot generate Objects/typeslots.inc, python not found !
Re-run configure with python in PATH.
make
Xavier de Gaye added the comment:
Following (and thanks to :) Martin's review and comments, this new patch:
* does not use the not portable '-e' echo option
* uses single quotes (') to avoid the escaping
* improves the error message
“make touch” does not always fix the probl
Changes by Xavier de Gaye :
--
nosy: +haypo
stage: patch review -> commit review
___
Python tracker
<http://bugs.python.org/issue27472>
___
___
Python-bugs-lis
Xavier de Gaye added the comment:
The attached patch fixes the issue. There is at least already an existing test
case: test_subprocess.MiscTests.test_getoutput calls
subprocess.getstatusoutput() that runs a Popen instance with shell=True.
--
stage: -> patch review
Added file: h
Changes by Xavier de Gaye :
--
nosy: +haypo
___
Python tracker
<http://bugs.python.org/issue16255>
___
___
Python-bugs-list mailing list
Unsubscribe:
Xavier de Gaye added the comment:
So the error message could be ('$@' being the target):
Cannot generate $@, python not found !
To skip re-generation of $@ run 'make touch' or 'make -t $@'.
Otherwise, set python in PATH and run configure or run make with
PYTHON_FO
Xavier de Gaye added the comment:
Issue 24034 is a duplicate.
--
___
Python tracker
<http://bugs.python.org/issue26662>
___
___
Python-bugs-list mailing list
Unsub
Xavier de Gaye added the comment:
New patch that does not call sysconfig.get_config_var() on platforms that have
'/bin/sh'.
--
Added file: http://bugs.python.org/file43809/unix_shell_16255_2.patch
___
Python tracker
<http://bu
Xavier de Gaye added the comment:
> The python '-E' option was needed on 3.4 when this patch was first
> implemented and is not needed anymore
See msg 269359 in issue 22724.
--
___
Python tracker
<http://bugs.py
Changes by Xavier de Gaye :
--
stage: test needed -> patch review
___
Python tracker
<http://bugs.python.org/issue26859>
___
___
Python-bugs-list mai
Xavier de Gaye added the comment:
New patch with cosmetic changes.
--
assignee: -> xdegaye
stage: -> patch review
Added file: http://bugs.python.org/file43817/test_getgroups_2.patch
___
Python tracker
<http://bugs.python.org/i
Xavier de Gaye added the comment:
Larry asked in msg 270937:
> Is there a plan to make Android a supported platform in 3.6?
This is the list of Android related issues that will modify the standard
library and core Python when fixed:
issue 16255: subrocess.Popen needs /bin/sh but Andr
Xavier de Gaye added the comment:
> Is there a plan to make Android a supported platform in 3.6?
Answer in the Android meta-issue at msg 270942.
--
___
Python tracker
<http://bugs.python.org/issu
Xavier de Gaye added the comment:
Patch with a new error message.
--
Added file: http://bugs.python.org/file43829/py_for_gen_26662_3.patch
___
Python tracker
<http://bugs.python.org/issue26
Changes by Xavier de Gaye :
--
resolution: -> fixed
stage: commit review -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Changes by Xavier de Gaye :
Added file: http://bugs.python.org/file43860/strace-pydebug.txt
___
Python tracker
<http://bugs.python.org/issue27606>
___
___
Python-bug
Changes by Xavier de Gaye :
Added file: http://bugs.python.org/file43861/logcat-pydebug.txt
___
Python tracker
<http://bugs.python.org/issue27606>
___
___
Python-bug
Changes by Xavier de Gaye :
Added file: http://bugs.python.org/file43859/logcat.txt
___
Python tracker
<http://bugs.python.org/issue27606>
___
___
Python-bugs-list mailin
New submission from Xavier de Gaye:
Android ndk version r11c.
The crash happens very early on python startup. The SIGILL occurs when python
is built 'with-pydebug'.
Python runs fine on the armv5te emulator when built with clang without
'-mthumb'.
Python runs fine on
Xavier de Gaye added the comment:
issue #27606: Android cross-built for armv5te with clang and '-mthumb' crashes
with SIGSEGV or SIGILL
--
dependencies: +Android cross-built for armv5te with clang and '-mthumb' crashes
wi
Xavier de Gaye added the comment:
The reference to '-mthumb' in the ndk documentation:
https://developer.android.com/ndk/guides/standalone_toolchain.html#abi.
--
___
Python tracker
<http://bugs.python.o
Xavier de Gaye added the comment:
The previous patch was using awkwardly, a 'host_cpu' configure argument to
specify the arm ABI and missed setting LDFLAGS for the armv7 ABI.
This patch instead uses the __ARM_ARCH macro defined by each compiler of the
Android toolchains:
echo
Changes by Xavier de Gaye :
--
nosy: +haypo
stage: patch review -> commit review
___
Python tracker
<http://bugs.python.org/issue26944>
___
___
Python-bugs-lis
Xavier de Gaye added the comment:
Thanks for the review and the suggestions Martin :)
New patch.
--
Added file: http://bugs.python.org/file43875/build-flags_3.patch
___
Python tracker
<http://bugs.python.org/issue26
Xavier de Gaye added the comment:
> Hum, does the id program supports -G on Android?
It does on Android 6.0 but prints the same result as 'id' (without -G) on
previous Android versions.
Here is the output of the commands involved in the test for the root user on my
archlinux box
Changes by Xavier de Gaye :
Added file: http://bugs.python.org/file43878/build-flags_3.patch
___
Python tracker
<http://bugs.python.org/issue26851>
___
___
Python-bug
Xavier de Gaye added the comment:
The first 'build-flags_3.patch' file that was uploaded did not get a review
button because ssh://h...@hg.python.org/cpython was down at that time.
The second upload has been successfull !
--
___
Pyth
Xavier de Gaye added the comment:
The test is already skipped by the patch, for Android API level < 23, with the
statement:
raise unittest.SkipTest("need working 'id -G'")
Do you mean that the test should be skipped instead more explicitly with
so
Xavier de Gaye added the comment:
Thanks for the suggestion, I won't include them anymore in patches then.
--
___
Python tracker
<http://bugs.python.org/is
Xavier de Gaye added the comment:
New patch. The sed commands used to evaluate ANDROID_API_LEVEL and _arm_arch do
not need to discard comment lines and empty lines in the output of the
preprocessor.
--
Added file: http://bugs.python.org/file43893/build-flags_4.patch
Changes by Xavier de Gaye :
--
resolution: -> fixed
stage: commit review -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Xavier de Gaye added the comment:
Thanks for looking into that problem.
Can you provide a patch ?
--
___
Python tracker
<http://bugs.python.org/issue26
Xavier de Gaye added the comment:
issue #27627: clang fails to build ctypes on Android armv7
--
dependencies: +clang fails to build ctypes on Android armv7
___
Python tracker
<http://bugs.python.org/issue26
New submission from Xavier de Gaye:
The build is done with:
clang --sysroot=/opt/android-ndk/platforms/android-21/arch-arm -target
armv7-none-linux-androideabi -gcc-toolchain
/opt/android-ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64
The error message:
clang --sysroot=/opt
Xavier de Gaye added the comment:
See also msg 269907 and msg269908.
--
___
Python tracker
<http://bugs.python.org/issue27627>
___
___
Python-bugs-list mailin
Xavier de Gaye added the comment:
> Cross-compile CPython for ARM with clang fails in _ctypes due to
> https://llvm.org/bugs/show_bug.cgi?id=20595. This bug is already fixed in
> libffi.
I have entered issue 27627 for this problem.
--
nosy:
Xavier de Gaye added the comment:
Nice, the patch fixes the problem when python is built with gcc :)
Running test_ctypes on the Android emulator when python is built for the arm
architecture or the armv7 architecture gives in both cases the same successfull
result:
Ran 456 tests in
Xavier de Gaye added the comment:
> After several years there is still no consenus, so make it simple - the popen
> and subprocess shell is one of /bin/sh, cmd.exe, or some other "hard-coded"
> shell.
I agree, the last patch that is being reviewed in issue 16255 a
New submission from Xavier de Gaye:
Do not install the Python test suite when configure is run with
'--disable-test-suite'. This about divides by two the size of the installed
standard library.
Related to issue 26852: add the '--enable-legacy-pyc-files' option to conf
Changes by Xavier de Gaye :
Added file: http://bugs.python.org/file43918/listdirs.py
___
Python tracker
<http://bugs.python.org/issue27640>
___
___
Python-bugs-list mailin
Changes by Xavier de Gaye :
--
components: +Cross-Build
nosy: +Alex.Willmer
___
Python tracker
<http://bugs.python.org/issue27640>
___
___
Python-bugs-list mailin
Xavier de Gaye added the comment:
Install byte-code files to their legacy locations and names to save space
(default are the PEP 3147 locations and names) when configure is run with
'--enable-legacy-pyc-files'.
The patch does not prevent ensurepip to use PEP 3147 locations and name
Xavier de Gaye added the comment:
issue #27640: add the '--disable-test-suite' option to configure
--
dependencies: +add the '--disable-test-suite' option to configure
___
Python tracker
<http://bug
Changes by Xavier de Gaye :
--
nosy: +haypo, thomas-petazzoni
___
Python tracker
<http://bugs.python.org/issue27640>
___
___
Python-bugs-list mailing list
Unsub
Changes by Xavier de Gaye :
--
nosy: +haypo, thomas-petazzoni
___
Python tracker
<http://bugs.python.org/issue26852>
___
___
Python-bugs-list mailing list
Unsub
Xavier de Gaye added the comment:
> hmm, I really don't buy the space-saving argument. you are saving some space
> with shorter path names, nothing more. so why do you introduce this option?
No, compileall is run with '-b', so there are no PEP 3147 __pycache__
dir
Xavier de Gaye added the comment:
> I am still curious what configures the preprocessor to set __ARM_ARCH to 7 (I
> guess the clang -target argument?)
Yes, the -target clang argument or the -march gcc argument.
> and why we can’t set LDFLAGS at the same time or place. Is it
Xavier de Gaye added the comment:
> but these are rebuilt when you start the interpreter, aren't they?
No.
Quoting PEP 3147:
Case 4: legacy pyc files and source-less imports
Python will ignore all legacy pyc files when a source file exists next to
it. In other words, if a
Xavier de Gaye added the comment:
Yes, the packager must use appropriately either CFLAGS CPPFLAGS [1] and
LDFLAGS, or CC. I am using:
CC="clang --sysroot=$(SYSROOT) -target $(TARGET) -gcc-toolchain
$(GCC_TOOLCHAIN)".
[1] See issue 27453, for the remaining problem upon usin
Xavier de Gaye added the comment:
> and if the only reason is to reduce space by omitting the source, then it
> should also not install the source so the name is wrong :)
I miss your point, msg271515 said earlier "the patch removes all *.py files".
The patch does a sourceless
Xavier de Gaye added the comment:
> About doko's note and your response: unless this patch does not install the
> source (I haven't looked), the __pycache__ files *will* be rebuilt at
> interpreter start, according to the text you quoted.
Right, and since the source fil
Xavier de Gaye added the comment:
Roman, can you please enter a new issue for that problem.
--
___
Python tracker
<http://bugs.python.org/issue26865>
___
___
Pytho
Xavier de Gaye added the comment:
> Some dependent issues, like issue26852, issue26859 and issue27640, are for
> reducing the size of an installation. How about moving them to another
> meta-issue? First they are not critical for normal usages on Android. Second
> they are no
Changes by Xavier de Gaye :
--
nosy: +thomas-petazzoni
___
Python tracker
<http://bugs.python.org/issue23968>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Xavier de Gaye :
--
nosy: +thomas-petazzoni
___
Python tracker
<http://bugs.python.org/issue27453>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Xavier de Gaye :
--
nosy: +thomas-petazzoni
___
Python tracker
<http://bugs.python.org/issue22724>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Xavier de Gaye :
--
nosy: +thomas-petazzoni
___
Python tracker
<http://bugs.python.org/issue27606>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Xavier de Gaye :
--
nosy: +thomas-petazzoni
___
Python tracker
<http://bugs.python.org/issue27627>
___
___
Python-bugs-list mailing list
Unsubscribe:
Xavier de Gaye added the comment:
Thanks for the review Martin. I will update the patch accordingly later.
--
___
Python tracker
<http://bugs.python.org/issue27
Changes by Xavier de Gaye :
--
nosy: +haypo
stage: -> commit review
___
Python tracker
<http://bugs.python.org/issue27453>
___
___
Python-bugs-list mai
Xavier de Gaye added the comment:
To reproduce the problem on any system where Python is built with configure:
$ mkdir -p tmp/build tmp/install
$ cd tmp
$ hg clone https://hg.python.org/cpython cpython
$ cd build
$ $(cd ../cpython && pwd)/configure --prefix=$(cd ../install &&a
Changes by Xavier de Gaye :
--
nosy: +xdegaye
___
Python tracker
<http://bugs.python.org/issue27641>
___
___
Python-bugs-list mailing list
Unsubscribe:
Xavier de Gaye added the comment:
Nice.
FWIW cross-compilation for Android works fine with comment-out-regen.patch.
> In native compiling mode, everything should be as normal. When
> cross-compiling, the rules for regenerating files should read like
>
> Python/importlib.h: # $
Xavier de Gaye added the comment:
> By msg264746, only ARM fails, so I patch libffi for arm and aarch64 triplets
> only
Why not for all Android architectures (*-linux-android*) as it is done in PR120
?
--
stage: -> patch review
___
Pytho
Xavier de Gaye added the comment:
Thanks for the patch Chi Hsuan Yen!
--
resolution: -> fixed
stage: commit review -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Xavier de Gaye added the comment:
We should wait for the pull request to be merged in the libffi development repo
before committing the patch. The PR is at
https://github.com/libffi/libffi/pull/265.
--
___
Python tracker
<http://bugs.python.
Xavier de Gaye added the comment:
This problem occured for the first time on the "installed Python" buildbot
(setup by Zachary) at
http://buildbot.python.org/all/builders/x86%20Gentoo%20Installed%20with%20X%203.x/builds/747
on the day changeset 78d2cb7f66b6 has been commited (see
Xavier de Gaye added the comment:
The reason I would like this problem fixed is that the test suite is run on an
installed Python when cross-compiling, obviously you cannot run the test suite
with the cross-compiled Python on the source tree of the build system
Xavier de Gaye added the comment:
It is also broken for gcc, see the buildbot 'compile' output.
It seems broken for all non windows builds whatever the compiler.
--
___
Python tracker
<http://bugs.python.o
Xavier de Gaye added the comment:
Patch rebased to current tip.
To summarize:
* The root cause of the problem reported by Benedikt still exists.
* The problem is hidden now that the shared libraries names include the
PLATFORM_TRIPLET.
* But byte-compilation still fails for cross-builds when
Xavier de Gaye added the comment:
> A question: should I include changes to configure and pyconfig.h.in in the
> patch?
You just need to mention that one should run autoreconf.
--
___
Python tracker
<http://bugs.python.org/i
Xavier de Gaye added the comment:
issue #27659: Check for the existence of crypt()
--
dependencies: +Check for the existence of crypt()
___
Python tracker
<http://bugs.python.org/issue26
Xavier de Gaye added the comment:
This is fixed in python 3.2 by changeset 670d4cbf1464, and indeed the
'>>' marker is shown at line 8 of pdb_list_bug_reproduce.py when
debugging this (modified for py3) script with python 3.2.
-
New submission from Xavier de Gaye:
It seems that using f_trace in the f_lineno getter PyFrame_GetLineNumber(), as
the condition to decide when tracing is active, is incorrect.
See the following two examples.
In the backtrace printed by tracer.py running with python 3.3,
the last entry should
Changes by Xavier de Gaye :
Added file: http://bugs.python.org/file29163/generator.py
___
Python tracker
<http://bugs.python.org/issue17277>
___
___
Python-bugs-list m
Xavier de Gaye added the comment:
The patch (on the default branch) reverts one of the changes made in r72488 to
introduce the new PyFrame_GetLineNumber() function (issue 5954): tb_lineno is
now back again the result of the call to PyCode_Addr2Line() instead of the
call to PyFrame_GetLineNumber
Xavier de Gaye added the comment:
The proposed patch fixes the backtrace line numbers issue, but it does not fix
PyFrame_GetLineNumber() which is the recommended way to get the frame line
number.
As mentionned in the original message, testing for f->f_trace to implement the
f_lineno getter
Xavier de Gaye added the comment:
> fix the issue by changing PyFrame_GetLineNumber() and the f_lineno accessors
The new patch named traced_frame.patch has been uploaded.
Also, now it is not allowed anymore to set the f_lineno attribute of a frame
that is not the frame being traced, as f_la
New submission from Xavier de Gaye:
On python 3.3 and the default branch, the jump from a 'return' fails although
the change to f_lineno is validated, see below.
This problem does not occur with python 2.7.
$ python return.py
> /tmp/return.py(8)()
-> foo()
(Pdb) break 5
Brea
Xavier de Gaye added the comment:
Oops, it occurs too with python 2.7.
--
versions: +Python 2.7
___
Python tracker
<http://bugs.python.org/issue17288>
___
___
Xavier de Gaye added the comment:
There is an error in my patch (already fixed in pdb-clone) and in Jyrki's patch.
Running Jyrki's patch on quit.py produces the following output where the line
number in the last entry of the backtrace is incorrect (should be line 9 instead
of line 7):
Xavier de Gaye added the comment:
The patch changes the semantics of the quit command: quit behaves like the gdb
detach command when pdb is started with set_trace.
--
Added file: http://bugs.python.org/file29232/branch-27.patch
___
Python tracker
Xavier de Gaye added the comment:
The traced_frame.patch fixes also issue 7238 and issue 16482.
--
___
Python tracker
<http://bugs.python.org/issue17277>
___
___
Xavier de Gaye added the comment:
Nosying Benjamin Peterson who knows frame_setlineno (issue 14612) and nosying
Jesús Cea Avión. Hoping they don't mind.
This problem occurs also when setting f_lineno from an exception debug event.
One may crash the interpreter (or get a "SystemErro
Xavier de Gaye added the comment:
The proposed patch fixes the problem:
* f_lineno cannot be set now from an exception trace function or from a return
trace function.
* The broken arithmetic involving a null pointer (f->f_stacktop, at the end of
frame_setlineno when popping blocks that
Xavier de Gaye added the comment:
Must add for completeness that f_lineno must be valid within a return trace
function for the reasons explained in the last paragraph of
Objects/lnotab_notes.txt.
--
___
Python tracker
<http://bugs.python.
Xavier de Gaye added the comment:
The call to set_trace() installs a local trace function on all the
frames of the stack, including on the oldest frame, i.e. the module
level frame. This causes the invocation of frame_settrace() in
frameobject.c and the module frame f_lineno is evaluated by
Xavier de Gaye added the comment:
The last patch proposed at issue 17277 and named traced_frame.patch
fixes also issue 17697, and issues 7238, 16482. IMHO one should remove
the assumption in PyFrame_GetLineNumber() that f_lineno is correct
when f_trace is not NULL, as there does not seem to be a
Xavier de Gaye added the comment:
Forgot to say that traced_frame.patch includes a test.
--
___
Python tracker
<http://bugs.python.org/issue16482>
___
___
Pytho
Xavier de Gaye added the comment:
The attached script, test_initiate_send.py, tests initiate_send with
threads, causing duplicate writes and an IndexError. This is the
script output using python on the default branch:
$ python test_initiate_send.py
--- Test: duplicate data sent ---
chat.send
Xavier de Gaye added the comment:
For the reson why read() must still check for EWOULDBLOCK even though
after select() has reported a file descriptor ready for reading, see
the BUGS section of select linux man page, which says:
Under Linux, select() may report a socket file descriptor as
Xavier de Gaye added the comment:
> Deciding what's best to do at this point without breaking existent
> code is not easy, that is why I think that on python <= 3.3 we
> should fix *asynchat* in order to take EAGAIN/EWOULDBLOCK into
> account and leave asyncore's re
New submission from Xavier de Gaye:
This does not happen on tests run with '-R 22:22' or a lower run count, but
occur systematically with '-R 23:23' or a greater run count.
$ ./python
Python 3.5.0a0 (default:1e1c6e306eb4, Oct 9 2014, 19:52:59)
[GCC 4.9.1 20140903 (prerel
1101 - 1200 of 1614 matches
Mail list logo
