Python recipes wanted?

Python recipes wanted?

[Craig McQueen]

I have made a number of recipes for Python packages, for my own use. Does meta-oe have an interest in any/all Python package recipe contributions, or ones that are considered more popular?

I have:

python3-aiohttp_2.2.3.bb
python3-aiohttp-jinja2_0.13.0.bb
python3-aiohttp-session_1.0.0.bb
python3-async-timeout_1.2.1.bb
python3-cobs_1.1.3.bb
python3-colorlog_2.10.0.bb
python3-configargparse_0.12.0.bb
python3-lru-dict_1.1.6.bb
python3-pycrypto_2.6.1.bb
python3-pyserial-asyncio_0.4.bb
python3-uvloop_0.8.0.bb
python3-yarl_0.11.0.bb

python-cobs_1.1.3.bb
python-lru-dict_1.1.6.bb

-- 
Craig McQueen

Re: Python recipes wanted?

[Tim Orling]

[-- Attachment #1: Type: text/plain, Size: 3423 bytes --]

When you say "meta-oe", I assume you mean "meta-openembedded/meta-python"
[1]. That layer is where they belong.

There is no rule as to what is "wanted", but since you took the trouble to
write recipes, we can all benefit from your effort. But, I would add some
general guidelines:

1. Make sure the python package is the latest release and the patch applies
on top of "master".
2. Use the pypi.bbclass [2] with  "inherit pypi" to simplify the recipe (no
SRC_URI for pythonhosted is needed)
3. Many folks are still using Python 2 as well, so many recipes put the
heart of the metadata in an ".inc" file and the ${PYTHON_PN} (expands to
python or python3) version specific things (e.g. "inherit setuptools3") in
the .bb file. There are many examples in meta-python. This is not a
requirement, but is strongly encouraged.
4. Help maintain the recipes in meta-python. Don't just send your recipe
and never look at it again. The amount of metadata in meta-openembedded is
a challenge to maintain [3]. Maintenance is aided by, for instance, adding
INHERIT += "distrodata" [4] to your local.conf and running "bitbake
python-foo -c check_pkg" to check for new upstream versions [5]. You can
also run "distrodata" on your entire image [6]. This can be automated.

Also, looking at your python*-uvloop issue on Github [7], if upstream does
not want the patches that is OK, just include them with your recipe for
meta-python and put "Upstream-Status: Inappropriate (embedded specific)" or
similar in the patch itself. See the commit patch message guidelines [8].
You should also follow the README in meta-python [9] and the OpenEmbedded
patch submission guidelines [10].

[1] http://git.openembedded.org/meta-openembedded/tree/meta-python
[2]
http://git.openembedded.org/meta-openembedded/tree/meta-python/classes/pypi.bbclass
[3]
http://www.openembedded.org/wiki/Bitbake_World_Status_Rocko#Failed_tasks_2017-08-31
[4]
http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#ref-classes-distrodata
[5]
http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#structure-build-tmp-log
[6]
http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-tasks-distrodata
[7] https://github.com/MagicStack/uvloop/issues/104
[8] http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
[9] http://git.openembedded.org/meta-openembedded/tree/meta-python/README
[10] http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded

On Thu, Aug 31, 2017 at 6:40 PM, Craig McQueen <craig.mcqueen@innerrange.com
> wrote:

> I have made a number of recipes for Python packages, for my own use. Does
> meta-oe have an interest in any/all Python package recipe contributions, or
> ones that are considered more popular?
>
> I have:
>
> python3-aiohttp_2.2.3.bb
> python3-aiohttp-jinja2_0.13.0.bb
> python3-aiohttp-session_1.0.0.bb
> python3-async-timeout_1.2.1.bb
> python3-cobs_1.1.3.bb
> python3-colorlog_2.10.0.bb
> python3-configargparse_0.12.0.bb
> python3-lru-dict_1.1.6.bb
> python3-pycrypto_2.6.1.bb
> python3-pyserial-asyncio_0.4.bb
> python3-uvloop_0.8.0.bb
> python3-yarl_0.11.0.bb
>
> python-cobs_1.1.3.bb
> python-lru-dict_1.1.6.bb
>
> --
> Craig McQueen
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

[-- Attachment #2: Type: text/html, Size: 6468 bytes --]