<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta/recipes-devtools/python/python3-nose_1.3.7.bb, branch mickledore-next</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=mickledore-next</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=mickledore-next'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2022-02-25T15:07:51+00:00</updated>
<entry>
<title>python3-nose: drop recipe</title>
<updated>2022-02-25T15:07:51+00:00</updated>
<author>
<name>Tim Orling</name>
<email>ticotimo@gmail.com</email>
</author>
<published>2022-02-22T19:16:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=974a5d72ea1173b1dd2ab7fc39759d4eb73180bf'/>
<id>urn:sha1:974a5d72ea1173b1dd2ab7fc39759d4eb73180bf</id>
<content type='text'>
The code has not been touched since 2016 and numerous files still have
Python2 syntax code in them. This causes do_compile errors when
packaging a wheel (PEP-517 packaging).

Nothing in oe-core depends on python3-nose.

[YOCTO #14638]

(From OE-Core rev: 19135f8b7cbaabeb2e38572d11e909ce386d60b8)

Signed-off-by: Tim Orling &lt;tim.orling@konsulko.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>python-nose: python3-nose should be default</title>
<updated>2019-06-12T09:54:39+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@intel.com</email>
</author>
<published>2019-06-11T10:10:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=0191f500c5b661652d0387c99ba6262979c08293'/>
<id>urn:sha1:0191f500c5b661652d0387c99ba6262979c08293</id>
<content type='text'>
We have nose recipes for both Py2 and Py3, but they both want to ship the
unversioned nosetest binary.  As Py2 is approaching EOL, remove the unversioned
binary from python-nose (leaving nosetest-2.7) instead of renaming the binary to
nosetest3 in python3-nose.

(From OE-Core rev: e22111a18a0f67fefd1800f67bd5e45637deaa60)

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>python-nose: use pypi.bbclass</title>
<updated>2017-12-13T14:00:52+00:00</updated>
<author>
<name>Tim Orling</name>
<email>timothy.t.orling@linux.intel.com</email>
</author>
<published>2017-11-19T00:19:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a61146fe9d129f28985ab28db56f7d4af71d34d1'/>
<id>urn:sha1:a61146fe9d129f28985ab28db56f7d4af71d34d1</id>
<content type='text'>
* Simplify python- and python3-nose by using pypi.bbclass
* Consolidate common content in python-nose.inc
  - Avoid duplication by using PYTHON_PN variable

(From OE-Core rev: 351e741cea4538cfe30640bd6e451c0fbc1d0329)

Signed-off-by: Tim Orling &lt;timothy.t.orling@linux.intel.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-nose: rename ${bindir}/nosetests into ${bindir}/nosetests3</title>
<updated>2017-05-18T13:01:48+00:00</updated>
<author>
<name>Denys Dmytriyenko</name>
<email>denys@ti.com</email>
</author>
<published>2017-05-09T19:31:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=1dda475da98835853a3500b616053f696b508210'/>
<id>urn:sha1:1dda475da98835853a3500b616053f696b508210</id>
<content type='text'>
This resolves a conflict when both python-nose and python3-nose are pulled
into an image and try to install ${bindir}/nosetests binary.

This matches with how other distros are solving this problem, e.g. Debian:
https://packages.debian.org/jessie/all/python3-nose/filelist

Also, other packages like python3-setuptools are already doing the same with
their binaries.

(From OE-Core rev: 1a3247d38939392bfdcb3eff1da7a1e08eff35f9)

Signed-off-by: Denys Dmytriyenko &lt;denys@ti.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>python: Several recipes needed SRC_URI updating</title>
<updated>2016-06-12T22:47:17+00:00</updated>
<author>
<name>Alejandro Hernandez</name>
<email>alejandro.hernandez@linux.intel.com</email>
</author>
<published>2016-06-09T17:00:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=5edb12b017eb1f2d330cec6dda71505018828fd7'/>
<id>urn:sha1:5edb12b017eb1f2d330cec6dda71505018828fd7</id>
<content type='text'>
Most python recipes download its source from pypi.python.org,
but they changed the way theyre storing the source code, so
we need to use pythonhosted instead, see:
https://bitbucket.org/pypa/pypi/issues/438/backwards-compatible-un-hashed-package

(From OE-Core rev: 08de9032e870966947b937a1226dd860e0bd71cf)

Signed-off-by: Alejandro Hernandez &lt;alejandro.hernandez@linux.intel.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-nose: add a recipe</title>
<updated>2016-06-01T11:38:42+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alexander.kanavin@linux.intel.com</email>
</author>
<published>2016-05-11T13:46:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a80a5b1f956d4d1ad0e998da10f31f81856b0309'/>
<id>urn:sha1:a80a5b1f956d4d1ad0e998da10f31f81856b0309</id>
<content type='text'>
This is needed for updating piglit to use Python 3.
Python 2 based recipe can be later moved to meta-oe.

(From OE-Core rev: 3e751bd05f7033b15e717fa4d56fefd915d2ea0c)

Signed-off-by: Alexander Kanavin &lt;alexander.kanavin@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
