While python3 module use cython to build library, the generated source file
is not stable at each build and made the generated library not be reproducible
This commit replaces un-predictable string with hardcode string in generated
source file to assure the generated library should be reproducible
(From OE-Core rev: 61d98d12eca1c7bdf3b7387a820c83d3b8fad965)
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changelog:
==========
- Some method calls with 0 or 1 argument failed to use ``PyObject_VectorCallMethod()``.
- Walrus assignments of literal Python integers could generate invalid C code.
(Github issue :issue:`6989`)
- ``cython.pythread_type_lock`` (also used as fallback for ``cython.pymutex``)
could stall on heavily contended locks.
(Github issue :issue:`6999`)
- C string arrays (not pointers) always coerced to the Python default string type,
even on explicit casts to other string types.
(Github issue :issue:`7020`)
- Unterminated ``\N{}`` character escapes in strings could unrail the parser.
(Github issue :issue:`7056`)
- An internal C function was not marked as ``static`` and leaked a linker symbol.
(Github issue :issue:`6957`)
- Some Unicode letters were not recognised as lexically valid name parts.
(Github issue :issue:`7059`)
- Compatibility with PyPy3.8 was lost by accident.
- The Linux binary wheels of 3.1.2 used SSSE3 CPU instructions which are not available on some CPUs.
(Github issue :issue:`7038`)
(From OE-Core rev: 14c2006bce8861eaf2b65d5c71097e67d1af19cf)
Signed-off-by: Liu Yiding <liuyd.fnst@fujitsu.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
