On 8/5/20 3:50 pm, Anders Montonen wrote:
On 8 May 2020, at 7:36, Chris Johns <chr...@rtems.org> wrote:
On 8/5/20 2:27 pm, Anders Montonen wrote:
Hi,
On 7 May 2020, at 5:10, Chris Johns <chr...@rtems.org> wrote:
On 7/5/20 9:37 am, Anders Montonen wrote:
This patch fixes the UnicodeDecodeError that randomly caused source
builder to hang.
In my testing, there was no difference in performance at least under
Python 3.
Have you tested python 2?
Unfortunately the patch caused the log.py module to trigger UnicodeEncodeErrors
under Python 2, so consider it withdrawn.
Oh ok. Is it worth looking at fixing log.py? Our fix seems to me to important.
I’m looking into it, I just wanted to give a heads-up.
Ok. I have been playing with a new version of log.py in rtems-tools to
avoid the "blocking while holding a lock" exception. I will send you a
copy off list. I am looking to use a queue and feed all the output to a
worker thread removing any locks. I am seeing the exception running
rtems-test with qemu with the xilinx_zynq_a9_qemu BSP.
On a not completely unrelated note, have there been any thoughts about setting
a timetable for deprecating Python 2 support now that it is EOL, eg. in RTEMS6?
Are there any specific host platforms you want to support that don’t have
Python 3?
We cannot just yet because we have users who run long life operating
systems and cannot move. This is one of the roles RTEMS provides. We
maintain tools and the OS longer than others and on older target
hardware. Large orgs cannot retool just because it exists.
Chris
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
