our requests. The irony is that the reason why I resigned from
being a core developer was because of the handling of this PR.
Xavier de Gaye
On Thu, Jun 16, 2022 at 7:54 PM Christian Heimes
wrote:
> On 16/06/2022 16.29, Xavier de Gaye wrote:
> > Victor Stinner wrote:
> > > ht
e Android team.
It is not clear how this backtrace can be missed when reading the issue !
There is also a patch provided in this issue that is straightforward and
that does not involve any change on distutils, only the Makefile and
configure.
Dave wrote:
> Xavier de Gaye reworked the build sys
On 3/23/20 11:17 PM, Leandro Müller wrote:
Hello Victor Stinner.
Thanks.
Your tip helped me a lot.
I understood that I need to get position on bycode of the line.
So I create the funcion to get position inside of the bycode.
Now I can to jump the correct position on trace.
frame->f_lasti = c
On 1/9/20 3:18 PM, Victor Stinner wrote:
Is the "ARM64" python-config (shell script) executed on the x86-64 host?
A cross-compilation means that there is probably no build framework on the
target platform and therefore the build configuration of the cross-compilation
of Python is not very
On 1/8/20 5:53 PM, Victor Stinner wrote:
You may get the wrong information if you pick the wrong python-config script :-(
IMHO we should add a new module (problem: how should it be called? pyconfig?)
The shell script python-config has been introduced by bpo issue 16235 named "Add
python-conf
Currently f_locals is documented as readonly [1].
The PEP says:
* "Don't change what isn't broken": the current tracing mode problems are caused
by a requirement that's specific to tracing mode (support for external
rebinding of function local variable references), so it made sense to also
The last post [1] in issue bpo-16079 lists the methods in Lib/test
that have duplicate names and that should be fixed.
Xavier
[1] https://bugs.python.org/issue16079#msg340168
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mail
Thanks.
Xavier
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
bedevere/issue-number and bedevere/news are not triggered for some
reason at https://github.com/python/cpython/pull/12708 and hang
forever with "Expected — Waiting for status to be reported ".
Xavier
___
Python-Dev mailing list
Python-Dev@python.org
http
Timeout (360 seconds) reached; failed to start emulator
---> Device ready.
---> Install Python on the emulator.
/home/pydev/build/python-native/python -B
/home/pydev/abifa/Android/tools/install.py
error: device 'emulator-5556' not found
I can reproduce this error after removing the kvm kernel m
you are definitively answering it or not.
The answer is yes indeed, it returns the target platform.
This is a listing of the non-obvious steps that lead to this conclusion.
Xavier
On 2/19/19 8:45 PM, Steve Dower wrote:
[Any reason for dropping python-dev?]
On 19Feb2019 1139, Xavie
https://gitlab.com/xdegaye/abifa
The table of content of the first url in my initial post gives also a
link to that repository.under the name 'Repository'.
Xavier
On Tue, Feb 19, 2019 at 4:54 PM Stephane Wirtel wrote:
>
> Hi Xavier,
>
> I get this exception
>
> Timeout (360 seconds) reached; fa
The following command runs the buildbottest on an Android emulator with docker
(it will use a little bit more than 11 GB):
$ docker run -it --privileged xdegaye/abifa:r14b-24-x86_64-master
This command does:
* pull an image from the Docker hub (only the first time that the command is
run,
On 06/06/2018 03:51 PM, Nick Coghlan wrote:
> On 6 June 2018 at 15:31, Rob Cliffe via Python-Dev mailto:python-dev@python.org>> wrote:
> ...
> *In other words, it looks as if in Python 3.6.5, the compiled list
comprehension**
> **can "see" a pre-existing global variable but not a local on
On 12/14/2017 02:59 PM, Victor Stinner wrote:
> It seems like Android is evolving quickly, would say quicker than
> Python releases. I'm asking if it's a good idea to put a recipe aside
> the Python source code for one specific Android API version? Would it
> still make sense to build for NDK v14
On 12/13/2017 10:56 PM, Victor Stinner wrote:
> I looked at your scripts to build Android but I failed to use them.
You failed because you did not read the README and tried to improvise. I will change the documentation and the build process to make it simpler for those that do not have the time t
On 12/11/2017 04:14 PM, Victor Stinner wrote:
> I'm asking for precise hardware specifications since Red Hat may be
> able to provide one through the https://osci.io/ program.
Is it acceptable to run the arm buildbots only on a weekly basis ?
For all the architectures (x86_64, armv7 and arm64),
On 12/11/2017 03:58 PM, Carl Bordum Hansen wrote:
>
> I've been lurking at your progress with android support for about a year, and
now that it is closing in I simply have to ask: what does it actually mean that
android is supported? That Android apps
> will be easy to develop in Python? That I
On 12/11/2017 03:40 PM, Victor Stinner wrote:
> 2017-12-11 14:58 GMT+01:00 Xavier de Gaye :
>> The host running the buildbots must be able to run 6 (i.e. 3 x (version 3.x
>> + maintenance version)) emulators simultaneously, so with an eight core cpu,
>> that will be 6 cores
On 12/11/2017 12:56 PM, Victor Stinner wrote:
> 2017-12-10 15:19 GMT+01:00 Xavier de Gaye :
>> * Given the cpu resources required to run the test suite on the arm
>> emulators,
>>it may be difficult to find a contributed buildbot worker. So it remains
>> to
>
On 12/10/2017 11:07 PM, Ned Deily wrote:
> On the one hand, it would be nice to have. But on the other, it does add a large non-zero burden to all core developers and to the release teams, to the minimum extent of trying to make sure that
all ongoing changes don't break platform support.
Yes t
On 12/10/2017 10:27 PM, Skip Montanaro wrote:
> I'm not familiar with software development on/for Android, but
> wouldn't official support also involve suitable package creation or
> does that just fall out for free from the build-for-emulator PR?
>
> Skip
>
The build-for-emulator PR allows build
On 12/10/2017 09:27 PM, Brett Cannon wrote:
> While the note from a technical standpoint is interest, Xavier, I don't quite
see what needs to be done to support Android at this point. Are you simply asking
we add Android API 24 as an official
> platform? Or permission to add your note to the Mis
The following note is a proposal to add the support of the Android platform.
The note is easier to read with clickable links at
https://github.com/xdegaye/cagibi/blob/master/doc/android_support.rst
Motivations
===
* Android is ubiquitous.
* This would be the first platform supported by
On 03/25/2017 08:57 PM, Terry Reedy wrote:
> On 3/25/2017 8:56 AM, Serhiy Storchaka wrote:
>> On 25.03.17 12:04, Victor Stinner wrote:
>>>
https://blog.jetbrains.com/pycharm/2017/03/inside-the-debugger-interview-with-elizaveta-shashkova/
>>>
>>>
>>> "What changed in Python 3.6 to allow this?
>>>
In PR 218 [1], INADA Naoki wrote:
> I think attributes of Python's code object is implementation detail, even
> though PyPy follows.
> But it's not big problem until there are some Python implementation
> having different code implementation.
Python's code object attributes are described in the D
On 01/14/2017 09:56 PM, Victor Stinner wrote:
> Great job! Thank you and Chi Hsuan Yen!
>
> Did you get feedback from users? Maybe from the Kivy community?
>
> Victor
>
> Le 14 janv. 2017 18:31, "Xavier de Gaye" a écrit :
>
> Only a few minor issues are l
Only a few minor issues are left to be fixed before the support of the
Android platform may be considered. See the current status at msg285493 [1]
in the Android meta-issue 26865 [2].
Xavier
[1] http://bugs.python.org/issue26865#msg285493
[2] http://bugs.python.org/issue26865
___
On 04/26/2016 07:12 PM, Stefan Krah wrote:
> Xavier de Gaye gmail.com> writes:
>> This code, or part of it, could be used to setup a buildbot and in this case
>> there would not be any conflict between the GPL v3 license and the Python
>> license, I think. I don't se
On 04/26/2016 04:14 PM, Ethan Furman wrote:
> On 04/24/2016 12:20 AM, Xavier de Gaye wrote:
>
>> [1] https://bitbucket.org/xdegaye/pyona/src
>
> The license:
> ---
> This software is licensed under the GNU General Public License version 3 or
later.
> --
On 04/26/2016 04:02 AM, Nick Coghlan wrote:
> On 26 April 2016 at 06:25, Xavier de Gaye mailto:xdeg...@gmail.com>> wrote:
>
> On 04/25/2016 04:53 PM, Stefan Krah wrote:
> > Eric Snow gmail.com <http://gmail.com>> writes:
> >> On Sun, Apr 24, 20
On 04/25/2016 04:53 PM, Stefan Krah wrote:
> Eric Snow gmail.com> writes:
>> On Sun, Apr 24, 2016 at 1:20 AM, Xavier de Gaye gmail.com>
> wrote:
>>> Starting with API level 21 (Android 5.0), the build of python3 with the
>>> official android toolchains (th
On 04/25/2016 04:36 PM, Eric Snow wrote:
> On Sun, Apr 24, 2016 at 1:20 AM, Xavier de Gaye wrote:
>> Starting with API level 21 (Android 5.0), the build of python3 with the
>> official android toolchains (that is, without resorting to external
>> libraries
>> for w
On 04/24/2016 11:50 AM, Stefan Krah wrote:
> Xavier de Gaye gmail.com> writes:
>> Starting with API level 21 (Android 5.0), the build of python3 with the
>> official android toolchains (that is, without resorting to external libraries
>> for wide character support) runs
Starting with API level 21 (Android 5.0), the build of python3 with the
official android toolchains (that is, without resorting to external libraries
for wide character support) runs correctly. With the set of patches described
in the patches/Makefile file at [1], the cpython test suite runs[2] o
On 03/14/2016 05:34 PM, Xavier de Gaye wrote:
> Changeset c2a53aa27cad [1] was commited in issue 22359 [2] to remove incorrect
> uses of recursive make. The changeset added executable binaries as
> prerequisites to the existing rules (Python/importlib.h and $(GRAMMAR_H)).
> This
On 03/14/2016 02:26 PM, R. David Murray wrote:
>
> The repo-timestamp problem is addressed by the 'make touch' target.
>
> And yes, checking in these platform-independent artifacts is very
> intentional: less to build, fewer external dependencies in the build
> process...you don't need to *have* p
On 07/31/2015 06:42 AM, Zachary Ware wrote:
On Thu, Jul 30, 2015 at 8:21 PM, Brett Cannon wrote:
Best thing I can think of is to post the Roundup search you did to find
those 400 so thoseof us who can help can just start whittling them away. You
could also share it with core-mentorship and ex
On 02/06/2015 11:48 PM, Francis Giraldeau wrote:
> 2015-02-06 6:04 GMT-05:00 Armin Rigo:
>
> Hi,
>
> On 6 February 2015 at 08:24, Maciej Fijalkowski mailto:fij...@gmail.com>> wrote:
> > I don't think it's safe to assume f_code is properly filled by the
> > time you might read it, d
On 03/02/2014 12:04 AM, Terry Reedy wrote:
> On 3/1/2014 3:25 PM, Antoine Pitrou wrote:
>> On Sat, 01 Mar 2014 15:08:00 -0500
>> Terry Reedy wrote:
>>> On 3/1/2014 2:57 PM, Sebastian Kraft wrote:
Hi everybody,
more than a year ago I have submitted a patch to enhance the Wave module
In issues 7238 [1], 16482 [2], 17697 [3] and 17277 [4], the line
number may be incorrect when the global trace function has been
removed but not the frame f_trace function.
A simple test (see below) in issue 17288 [5] crashes the interpreter
when setting f_lineno in a generator from a return trace
It happens that few tests are also never run because of name conflicts.
See issue 16056.
Xavier
On Wed, Aug 28, 2013 at 1:37 PM, Victor Stinner
wrote:
> Hi,
>
> I just noticed that tests using @requires_freebsd_version and
> @requires_linux_version decorator from test.support are never run
> sin
On Tue, Mar 26, 2013 at 2:28 PM, R. David Murray wrote:
> On Mon, 25 Mar 2013 18:16:47 -0700, Raymond Hettinger wrote:
>> If you're editing with Emacs, it is really easy to reflow paragraphs
>> and to insert or remove multiline comments each prefixed with #.
>> But with other editors, it can be a P
On Mon, Apr 30, 2012 at 12:31 PM, Xavier de Gaye wrote:
> Issue http://bugs.python.org/issue13183 raises the point that the step
> command of pdb is broken. This issue is 6 months old. A patch and test
> case have been proposed.
Other pdb commands are also broken for the same reason
On Mon, Apr 30, 2012 at 6:57 PM, Senthil Kumaran wrote:
> Irrespective of this - Issue13183 seems to be an easy to verify bug in
> 3.2 and 3.3. I think, it would most visible if you were to use a full
> screen debugger and you will notice that the return call indicator has
> jumped to the next stat
Issue http://bugs.python.org/issue13183 raises the point that the step
command of pdb is broken. This issue is 6 months old. A patch and test
case have been proposed. The 'Lifecycle of a Patch' at
http://docs.python.org/devguide/patch.html says
If your patch has not received any notice from review
46 matches
Mail list logo
