<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta/recipes-devtools/python/python3/python3-manifest.json, branch 2.7_M2</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=2.7_M2</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=2.7_M2'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2019-02-08T10:57:19+00:00</updated>
<entry>
<title>python3: tweaks to achieve 100% pass rate in ptest</title>
<updated>2019-02-08T10:57:19+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex.kanavin@gmail.com</email>
</author>
<published>2019-02-07T16:53:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=c92e780c85523fe860602b947b029d7782afa47a'/>
<id>urn:sha1:c92e780c85523fe860602b947b029d7782afa47a</id>
<content type='text'>
(From OE-Core rev: 22f4f1ef17219448416b7cf2a570c7acd7149a64)

Signed-off-by: Alexander Kanavin &lt;alex.kanavin@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>python3: upgrade to 3.7.2</title>
<updated>2019-02-08T10:57:19+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex.kanavin@gmail.com</email>
</author>
<published>2019-02-06T16:26:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=e2c3247c233876ab090c9ce3d5325a6d46ab350f'/>
<id>urn:sha1:e2c3247c233876ab090c9ce3d5325a6d46ab350f</id>
<content type='text'>
I took the same approach as the recent perl upgrade: write recipe from scratch,
taking the pieces from the old recipe only when they were proven to be necessary.

The pgo, manifest and ptest features are all preserved.

New features:

- native and target recipes are now unified into one recipe

- check_build_completeness.py runs right after do_compile() and verifies that
all optional modules have been built (a notorious source of regressions)

- a new approach to sysconfig.py and distutils/sysconfig.py returning values
appropriate for native or target builds: we copy the configuration file to a
separate folder, add that folder to sys.path (through environment variable
that differs between native and target builds), and point python to the file
through another environment variable.

There were a few other patches where it was difficult to decide if the patch
is still relevant, and how to test that it works correctly; please add those
as-needed by testing the new python.

(From OE-Core rev: 02714c105426b0d687620913c1a7401b386428b6)

Signed-off-by: Alexander Kanavin &lt;alex.kanavin@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>python3: Adds instructions to the manifest file</title>
<updated>2018-12-01T11:38:37+00:00</updated>
<author>
<name>Alejandro Enedino Hernandez Samaniego</name>
<email>alejandro.enedino.hernandez-samaniego@xilinx.com</email>
</author>
<published>2018-11-16T19:31:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=6c524c09067a57c6e78e41a3860387dd4b31dc2b'/>
<id>urn:sha1:6c524c09067a57c6e78e41a3860387dd4b31dc2b</id>
<content type='text'>
While there is a bit of documentation regarding building a new
manifest file for python, it seems that users usually only read
the manifest file.

The manifest file is in JSON format which doesn't allow comments,
hence why instructions were initially put elsewhere.

This patch hacks the call to open the JSON manifest file by using a
marker to trick it into reading only part of the file as the manifest
itself, and keep the other part as comments, which contain instructions
for the user to run the create_manifest task after an upgrade or when
adding a new package.

(From OE-Core rev: 3eab24c6dc095fd2305b9be8467aab1191141e35)

Signed-off-by: Alejandro Enedino Hernandez Samaniego &lt;alejandr@xilinx.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>python3: add tk support</title>
<updated>2018-11-23T23:35:19+00:00</updated>
<author>
<name>Mingli Yu</name>
<email>Mingli.Yu@windriver.com</email>
</author>
<published>2018-11-14T09:36:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=75d2d6776b434e998c0ad7ef531ce179d1595e7d'/>
<id>urn:sha1:75d2d6776b434e998c0ad7ef531ce179d1595e7d</id>
<content type='text'>
Add support to enable tk via PACKAGECONFIG.
before this patch:
 # python3
 Python 3.5.6 (default, Nov  8 2018, 04:53:45)
 [GCC 8.2.0] on linux
 Type "help", "copyright", "credits" or "license" for more information.
 &gt;&gt;&gt; import tkinter
 Traceback (most recent call last):
  File "&lt;stdin&gt;", line 1, in &lt;module&gt;
  File "/usr/lib64/python3.5/tkinter/__init__.py", line 35, in &lt;module&gt;
    import _tkinter # If this fails your Python may not be configured for Tk
 ImportError: No module named '_tkinter'
 &gt;&gt;&gt;

After this patch, if enable tk in PACKAGECONFIG, then
 # python3
 Python 3.5.6 (default, Nov  8 2018, 03:15:52)
 [GCC 8.2.0] on linux
 Type "help", "copyright", "credits" or "license" for more information.
 &gt;&gt;&gt; import tkinter
 &gt;&gt;&gt;

(From OE-Core rev: 4b781d545e7e0b084201cd6a8fad953b0f231513)

Signed-off-by: Mingli Yu &lt;Mingli.Yu@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>python3: add python3-venv to the python3-modules RDEPENDS</title>
<updated>2018-11-07T23:08:55+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@intel.com</email>
</author>
<published>2018-11-05T11:22:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=fc3af664f3ddfe5b6d20ac4469cb2ff52ba565d4'/>
<id>urn:sha1:fc3af664f3ddfe5b6d20ac4469cb2ff52ba565d4</id>
<content type='text'>
(From OE-Core rev: ed5e7541677f6a046f85389cd0c879be3db422cd)

Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>python3: Fix python3-pyvenv run-time dependency</title>
<updated>2018-11-07T23:08:55+00:00</updated>
<author>
<name>Hugues Kamba</name>
<email>Hugues.Kamba@arm.com</email>
</author>
<published>2018-10-30T09:37:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=0140a1c2f7501758615bfa59873fd00196ef6b72'/>
<id>urn:sha1:0140a1c2f7501758615bfa59873fd00196ef6b72</id>
<content type='text'>
Pyvenv is just a small script that uses venv to create virtual
environments.
https://www.python.org/dev/peps/pep-0405/#creating-virtual-environments

This patch adds the python3-venv module as a self-contained package which
python3-pyvenv must depend on at run-time.

The patch also provides the package python3-pyvenv from the pyhton3-venv
package.This is good for future-proofing since python3-pyvenv has been
deprecated and only python3-venv is now available in Python 3.6.
https://docs.python.org/3/library/venv.html.

Without this patch python3-pyvenv is broken because it is missing the
venv module at run-time. This patch specifies the newly created
python3-venv as a run-time dependency of python3-pyvenv.

(From OE-Core rev: effa141bfce55aab25142ee578c95383c755ad73)

Signed-off-by: Hugues Kamba &lt;hugues.kamba@arm.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>python3: move sqlite files into python-sqlite</title>
<updated>2018-10-01T12:04:49+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@intel.com</email>
</author>
<published>2018-09-28T16:06:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f51d0a19afeb3cf9b5bad6e3b470b2a8fb6065f8'/>
<id>urn:sha1:f51d0a19afeb3cf9b5bad6e3b470b2a8fb6065f8</id>
<content type='text'>
sqlite3/__init__.py was accidentally included in python3-misc.

(From OE-Core rev: 4e397e16996662bce51608cf5e20448b9803c476)

Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>python3: consolidate tests</title>
<updated>2018-09-22T01:45:46+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@intel.com</email>
</author>
<published>2018-09-14T11:27:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=e6aea815de48459e1910e58a9eda58aab57d5bbf'/>
<id>urn:sha1:e6aea815de48459e1910e58a9eda58aab57d5bbf</id>
<content type='text'>
Currently the bulk of the tests in python3-tests, some more in
python3-sqlite3-tests, and others in their parent module (such as
python3-ctypes).  This is pointless space usage if we're not planning on running
the tests, so consolidate all the tests into python3-tests.

(From OE-Core rev: 554d3690dab49fee3c93b6b677eb3ef58cff64c1)

Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>python3: don't sort the manifest in create_manifest</title>
<updated>2018-09-22T01:45:46+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@intel.com</email>
</author>
<published>2018-09-14T11:08:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=2ac291af1f10230525c331ea61e696fb00f2bc33'/>
<id>urn:sha1:2ac291af1f10230525c331ea61e696fb00f2bc33</id>
<content type='text'>
Instead of sorting the entire manifest when it is updated, use OrderedDict to
preserve the order of fields.  This means that packages can be ordered in the
manifest to allow non-trivial FILES assignments (such as a package that picks up
pieces of other packages)

The manifest has been regenerated with the new stable ordering, and
distutils-staticdev moved above distutils so the packaging rules work as
expected.

(From OE-Core rev: 1c67c2146e3644a26367a32885d27a4378f17ac6)

Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>python3-manifest: Avoid duplicate modules</title>
<updated>2018-09-06T09:36:31+00:00</updated>
<author>
<name>Alejandro Enedino Hernandez Samaniego</name>
<email>alejandro.enedino.hernandez-samaniego@xilinx.com</email>
</author>
<published>2018-09-05T06:45:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a8a984dde7e4227be5f2104643226575f5c58c59'/>
<id>urn:sha1:a8a984dde7e4227be5f2104643226575f5c58c59</id>
<content type='text'>
There was a bug where modules were being added twice to the
core package, this patches the manifest to reflect the fix on
the create_manifest script.

(From OE-Core rev: 9ddbff824052751b4d0bb30c453ecb5098d728c9)

Signed-off-by: Alejandro Enedino Hernandez Samaniego &lt;alejandr@xilinx.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
