[Bug 1595421] New: fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

List overview All Threads
Download

newer

older

[Bug 1543407] New:...

[Bug 1604733] New:...

bugzilla＠redhat.com

26 Jun 2018 26 Jun '18

10:50 p.m.

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Bug ID: 1595421 Summary: fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized Product: Fedora Version: rawhide Component: fontforge Assignee: kevin@scrye.com Reporter: mhroncok@redhat.com QA Contact: extras-qa@fedoraproject.org CC: fonts-bugs@lists.fedoraproject.org, kevin@scrye.com, paul@frixxon.co.uk, pnemade@redhat.com, vstinner@redhat.com

Description of problem: When other packages try to use fontforge in the f29-python side tag (with Python 3.7), it fails:

fontforge -lang=py -script apply_featurefile.py Lohit-Assamese.sfd Lohit-Assamese.fea Copyright (c) 2000-2014 by George Williams. See AUTHORS for Contributors. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html with many parts BSD http://fontforge.org/license.html. Please read LICENSE. Based on sources from 08:52 UTC 19-Jun-2018-ML-D. Based on source from git with hash: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

Version-Release number of selected component (if applicable): fontforge-20170731-6.fc29

_Py_InitializeCore can only be called once. See https://bugs.python.org/issue33932 or similar change in https://github.com/originell/jpype/pull/332

Even if this change might get reverted in 3.7, this will need to be fixed before 3.8 anyway.

-- You are receiving this mail because: You are on the CC list for the bug.

Show replies by date

bugzilla＠redhat.com

26 Jun 26 Jun

10:52 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Miro Hrončok mhroncok@redhat.com changed:

--- Comment #1 from Miro Hrončok mhroncok@redhat.com --- Victor, should I backport https://github.com/python/cpython/commit/3747dd16d5d2af3499f586386e49740a045... to our python3 package?

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

10:53 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

--- Comment #2 from Miro Hrončok mhroncok@redhat.com ---

...

_Py_InitializeCore can only be called once

Should have been:

...

Py_Initialize() can only be called once

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

10:54 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Miro Hrončok mhroncok@redhat.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1565020 (PYTHON37)

Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1565020 [Bug 1565020] Python 3.7

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

27 Jun 27 Jun

10:19 a.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Miro Hrončok mhroncok@redhat.com changed:

--- Comment #3 from Miro Hrončok mhroncok@redhat.com --- Ok, according to the release manager of 3.7, the fix will be in final 3.7.0, I'll backport it to unblock this.

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

10:20 a.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

--- Comment #4 from Miro Hrončok mhroncok@redhat.com --- Actually, 3.7.0 final is planned for today, so I'll just wait.

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

3:31 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

--- Comment #5 from Parag Nemade pnemade@redhat.com --- Thank you Miro for looking into this issue.

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

28 Jun 28 Jun

10:49 a.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

--- Comment #6 from Miro Hrončok mhroncok@redhat.com --- python3-3.7.0-1.fc29 built. will rebuild fontforge.

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

11:15 a.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Miro Hrončok mhroncok@redhat.com changed:

--- Comment #7 from Miro Hrončok mhroncok@redhat.com --- Built. Will try to build lohit-*-fonts to see if it's fixed.

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

11:25 a.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Miro Hrončok mhroncok@redhat.com changed:

--- Comment #8 from Miro Hrončok mhroncok@redhat.com --- fontforge -lang=py -script apply_featurefile.py Lohit-Assamese.sfd Lohit-Assamese.fea Copyright (c) 2000-2014 by George Williams. See AUTHORS for Contributors. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html with many parts BSD http://fontforge.org/license.html. Please read LICENSE. Based on sources from 09:57 UTC 28-Jun-2018-ML-D. Based on source from git with hash: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

OK, Victor, what now?

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

11:56 a.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

--- Comment #9 from Miro Hrončok mhroncok@redhat.com --- #0 0x00007ffff192a14b in raise () from /lib64/libc.so.6 #1 0x00007ffff19146d1 in abort () from /lib64/libc.so.6 #2 0x00007ffff61e4c6a in fatal_error.lto_priv () from /lib64/libpython3.7m.so.1.0 #3 0x00007ffff62420a4 in _Py_FatalInitError () from /lib64/libpython3.7m.so.1.0 #4 0x00007ffff6245b5f in pymain_main.constprop.357.cold () from /lib64/libpython3.7m.so.1.0 #5 0x00007ffff6245dfe in Py_Main () from /lib64/libpython3.7m.so.1.0 #6 0x00007ffff68bb063 in PyFF_Main () from /lib64/libfontforge.so.2 #7 0x00007ffff68deb4d in CheckIsScript () from /lib64/libfontforge.so.2 #8 0x00007ffff7a6ae62 in fontforge_main () from /lib64/libfontforgeexe.so.2 #9 0x00007ffff19162fb in __libc_start_main () from /lib64/libc.so.6 #10 0x000055555555496a in _start ()

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

1:42 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Victor Stinner vstinner@redhat.com changed:

--- Comment #10 from Victor Stinner vstinner@redhat.com --- Oh no. My change https://bugs.python.org/issue33932 didn't fix fontforge :-( fontforge calls Py_Initialize() and then Py_Main(). It seems like my fix doesn't cover this use case. I didn't expect that an application embeds Python using Py_Main(). For me, Py_Main() was only used by Python itself.

I reopened the issue upstream: https://bugs.python.org/issue33932#msg320665

For fontforge, the workaround/fix is to not call Py_Initialize() before Py_Main().

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

6:10 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

--- Comment #11 from Miro Hrončok mhroncok@redhat.com --- Victor, would you be able to provide a workaround patch for fontforge? Naively removing Py_Initialize doesn't solve this.

Program received signal SIGSEGV, Segmentation fault. 0x00007ffff629a9f5 in PyTuple_New () from /lib64/libpython3.7m.so.1.0 (gdb) backtrace #0 0x00007ffff629a9f5 in PyTuple_New () from /lib64/libpython3.7m.so.1.0 #1 0x00007ffff6279985 in PyType_Ready () from /lib64/libpython3.7m.so.1.0 #2 0x00007ffff62799b5 in PyType_Ready () from /lib64/libpython3.7m.so.1.0 #3 0x00007ffff68b5115 in CreatePyModule () from /lib64/libfontforge.so.2 #4 0x00007ffff68baa22 in FontForge_InitializeEmbeddedPython () from /lib64/libfontforge.so.2 #5 0x00007ffff68baf5c in PyFF_Main () from /lib64/libfontforge.so.2 #6 0x00007ffff68deafd in CheckIsScript () from /lib64/libfontforge.so.2 #7 0x00007ffff7a6ae62 in fontforge_main () from /lib64/libfontforgeexe.so.2 #8 0x00007ffff19162fb in __libc_start_main () from /lib64/libc.so.6 #9 0x000055555555496a in _start ()

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

30 Jun 30 Jun

8:42 a.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Nick Coghlan ncoghlan@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |ncoghlan@gmail.com

--- Comment #12 from Nick Coghlan ncoghlan@gmail.com --- As an interim workaround, I'd suggest trying a CPython patch that changes the following lines to return Py_INIT_OK() instead of reporting an error:

* https://github.com/python/cpython/blob/5bb5bbfca847524bab5f2368bdb48eedf5dba... * https://github.com/python/cpython/blob/5bb5bbfca847524bab5f2368bdb48eedf5dba...

I'm not sure it'll work, but it's worth a try to see if it's enough to emulate the old "It's like running Py_Main(), but without actually configuring the interpreter from the environment and command line properly" behaviour.

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

8:45 a.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

--- Comment #13 from Nick Coghlan ncoghlan@gmail.com --- The relevant upstream issue has moved: https://bugs.python.org/issue34008

This is due to the fact that Py_Main() doesn't call Py_Initialize() internally any more (which is why the fix for https://bugs.python.org/issue33932 didn't fix the fontforge failure after all).

Instead, both Py_Main() and Py_Initialize() call the new lower level interpreter bootstrapping API directly.

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

11:02 a.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Miro Hrončok mhroncok@redhat.com changed:

What |Removed |Added ---------------------------------------------------------------------------- External Bug ID| |Python 34008

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

noon

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

--- Comment #14 from Miro Hrončok mhroncok@redhat.com --- (In reply to Nick Coghlan from comment #12)

...

As an interim workaround, I'd suggest trying a CPython patch that changes the following lines to return Py_INIT_OK() instead of reporting an error:

https://github.com/python/cpython/blob/ 5bb5bbfca847524bab5f2368bdb48eedf5dba74f/Python/pylifecycle.c#L619

https://github.com/python/cpython/blob/ 5bb5bbfca847524bab5f2368bdb48eedf5dba74f/Python/pylifecycle.c#L797

I'm not sure it'll work, but it's worth a try to see if it's enough to emulate the old "It's like running Py_Main(), but without actually configuring the interpreter from the environment and command line properly" behaviour.

https://koji.fedoraproject.org/koji/taskinfo?taskID=27963735 in progress (I haven't disabled the tests to see if the test suite still works).

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

1:25 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

--- Comment #15 from Miro Hrončok mhroncok@redhat.com --- Fatal Python error: _Py_InitializeMainInterpreter: main interpreter already initialized

Current thread 0x00007ffff7fd1e80 (most recent call first):

Program received signal SIGABRT, Aborted. 0x00007ffff192809b in raise () from /lib64/libc.so.6 (gdb) backtrace #0 0x00007ffff192809b in raise () at /lib64/libc.so.6 #1 0x00007ffff19126f9 in abort () at /lib64/libc.so.6 #2 0x00007ffff61e3dac in fatal_error.lto_priv () at /lib64/libpython3.7m.so.1.0 #3 0x00007ffff6251035 in pathconfig_global_init.cold () at /lib64/libpython3.7m.so.1.0 #4 0x00007ffff6254e4d in pymain_main.constprop.361.cold () at /lib64/libpython3.7m.so.1.0 #5 0x00007ffff62558db in Py_Main () at /lib64/libpython3.7m.so.1.0 #6 0x00007ffff68bb063 in PyFF_Main () at /lib64/libfontforge.so.2 #7 0x00007ffff68deb4d in CheckIsScript () at /lib64/libfontforge.so.2 #8 0x00007ffff7a6ae62 in fontforge_main () at /lib64/libfontforgeexe.so.2 #9 0x00007ffff191425b in __libc_start_main () at /lib64/libc.so.6 #10 0x000055555555496a in _start ()

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

2 Jul 2 Jul

1:34 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Matěj Cepl mcepl@cepl.eu changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |mcepl@cepl.eu

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

7:20 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

--- Comment #16 from Miro Hrončok mhroncok@redhat.com --- The side tag is no more. This now affects rawhide.

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

5 Jul 5 Jul

2:05 a.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

--- Comment #17 from Parag Nemade pnemade@redhat.com --- It appears fontforge got built successfully now. As part of other bug 1596037 fix, Kevin attempted new fontforge build and its successful.

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

9:25 a.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

--- Comment #18 from Miro Hrončok mhroncok@redhat.com --- Fontforge builds from the start. It's:

lohit-assamese-fonts lohit-bengali-fonts lohit-devanagari-fonts lohit-gujarati-fonts lohit-gurmukhi-fonts lohit-malayalam-fonts lohit-marathi-fonts lohit-nepali-fonts lohit-odia-fonts lohit-tamil-fonts

that FTBFS due this bug.

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

10:04 a.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

--- Comment #19 from Parag Nemade pnemade@redhat.com --- Ah right, those fonts packages are FTBFS now.

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

12 Jul 12 Jul

4:35 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

--- Comment #20 from Victor Stinner vstinner@redhat.com --- I looked one more time to the issue:

* fontforge code is fine: it calls Py_Initialize() before using the Python C API to initialize its Python namespace (modules, functions, types, etc.), and later it calls Py_Main().

* Python 3.7.0 is wrong: it fails with a fatal erro when Py_Main() is called if Py_Initialize() has been called previously. It is a regression since it worked fine in Python 3.6.

* My PR https://github.com/python/cpython/pull/8043 works again the simplest test: "fontforge -script hello.py" where hello.py is just "print('Hello World!')"

* This PR is not enough according to Miro, since fontforge requires sys.argv to be set, whereas sys.argv is no longer set when Py_Main() is after Py_Initialize(): https://github.com/python/cpython/pull/8043#issuecomment-401731992

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

4:39 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Miro Hrončok mhroncok@redhat.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Assignee|mhroncok@redhat.com |vstinner@redhat.com

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

18 Jul 18 Jul

10:28 a.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

--- Comment #21 from Parag Nemade pnemade@redhat.com --- Any updates here please? I see those fonts are still FTBFS.

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

19 Jul 19 Jul

11:02 a.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Miro Hrončok mhroncok@redhat.com changed:

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

11:32 a.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Miro Hrončok mhroncok@redhat.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Priority|unspecified |high

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

20 Jul 20 Jul

4:40 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Victor Stinner vstinner@redhat.com changed:

--- Comment #22 from Victor Stinner vstinner@redhat.com ---

...

Any updates here please? I see those fonts are still FTBFS.

I updated my upstream PR https://github.com/python/cpython/pull/8043 to not only allow to call Py_Main() after Py_Initialize(), but also to update sys.argv from the new configuration.

Miro confirmed that my PR fixes fontforge: https://github.com/python/cpython/pull/8043#issuecomment-406629309

I just merged my PR to master and I'm backporting it to Python 3.7: https://github.com/python/cpython/pull/8352

Sorry for the delay, Python initialization code is very complex and so very fragile. I hesitated how to fix the ssue. I chose to write the smallest fix just to repair fontforge. More enhancements will only be done in the future Python 3.8.

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

4:52 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Miro Hrončok mhroncok@redhat.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |POST

--- Comment #23 from Miro Hrončok mhroncok@redhat.com --- https://src.fedoraproject.org/rpms/python3/pull-request/46

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

23 Jul 23 Jul

1:29 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Miro Hrončok mhroncok@redhat.com changed:

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

1:32 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Miro Hrončok mhroncok@redhat.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1604723

Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1604723 [Bug 1604723] lohit-assamese-fonts: FTBFS in Fedora rawhide

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

1:32 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Miro Hrončok mhroncok@redhat.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1604724

Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1604724 [Bug 1604724] lohit-bengali-fonts: FTBFS in Fedora rawhide

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

1:33 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Miro Hrončok mhroncok@redhat.com changed:

Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1604726 [Bug 1604726] lohit-devanagari-fonts: FTBFS in Fedora rawhide https://bugzilla.redhat.com/show_bug.cgi?id=1604728 [Bug 1604728] lohit-gujarati-fonts: FTBFS in Fedora rawhide https://bugzilla.redhat.com/show_bug.cgi?id=1604729 [Bug 1604729] lohit-gurmukhi-fonts: FTBFS in Fedora rawhide https://bugzilla.redhat.com/show_bug.cgi?id=1604730 [Bug 1604730] lohit-malayalam-fonts: FTBFS in Fedora rawhide https://bugzilla.redhat.com/show_bug.cgi?id=1604731 [Bug 1604731] lohit-marathi-fonts: FTBFS in Fedora rawhide https://bugzilla.redhat.com/show_bug.cgi?id=1604732 [Bug 1604732] lohit-nepali-fonts: FTBFS in Fedora rawhide

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

1:33 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Miro Hrončok mhroncok@redhat.com changed:

Referenced Bugs:

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

1:33 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Miro Hrončok mhroncok@redhat.com changed:

Referenced Bugs:

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

1:33 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Miro Hrončok mhroncok@redhat.com changed:

Referenced Bugs:

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

1:33 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Miro Hrončok mhroncok@redhat.com changed:

Referenced Bugs:

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

1:33 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Miro Hrončok mhroncok@redhat.com changed:

Referenced Bugs:

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

1:33 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Miro Hrončok mhroncok@redhat.com changed:

Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1604733 [Bug 1604733] lohit-odia-fonts: FTBFS in Fedora rawhide https://bugzilla.redhat.com/show_bug.cgi?id=1604734 [Bug 1604734] lohit-tamil-fonts: FTBFS in Fedora rawhide

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla＠redhat.com

1:33 p.m.

New subject: [Bug 1595421] fontforge on Python 3.7: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

https://bugzilla.redhat.com/show_bug.cgi?id=1595421

Miro Hrončok mhroncok@redhat.com changed:

Referenced Bugs:

-- You are receiving this mail because: You are on the CC list for the bug.

2271

Age (days ago)

2298

Last active (days ago)

fonts-bugs@lists.fedoraproject.org

40 comments

1 participants

tags (0)

participants (1)

bugzilla＠redhat.com