python: add qemu package installer
Add setup.cfg and setup.py, necessary for installing a package via
pip. Add a ReST document (PACKAGE.rst) explaining the basics of what
this package is for and who to contact for more information. This
document will be used as the landing page for the package on PyPI.
List the subpackages we intend to package by name instead of using
find_namespace because find_namespace will naively also packages tests,
things it finds in the dist/ folder, etc. I could not figure out how to
modify this behavior; adding allow/deny lists to setuptools kept
changing the packaged hierarchy. This works, roll with it.
I am not yet using a pyproject.toml style package manifest, because
"editable" installs are not defined (yet?) by PEP-517/518.
I consider editable installs crucial for development, though they have
(apparently) always been somewhat poorly defined.
Pip now (19.2 and later) now supports editable installs for projects
using pyproject.toml manifests, but might require the use of the
--no-use-pep517 flag, which somewhat defeats the point. Full support for
setup.py-less editable installs was not introduced until pip 21.1.1:
https://github.com/pypa/pip/pull/9547/commits/7a95720e796a5e56481c1cc20b6ce6249c50f357
For now, while the dust settles, stick with the de-facto
setup.py/setup.cfg combination supported by setuptools. It will be worth
re-evaluating this point again in the future when our supported build
platforms all ship a fairly modern pip.
Additional reading on this matter:
https://github.com/pypa/packaging-problems/issues/256
https://github.com/pypa/pip/issues/6334
https://github.com/pypa/pip/issues/6375
https://github.com/pypa/pip/issues/6434
https://github.com/pypa/pip/issues/6438
Signed-off-by: John Snow <jsnow@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Cleber Rosa <crosa@redhat.com>
Message-id: 20210527211715.394144-11-jsnow@redhat.com
Signed-off-by: John Snow <jsnow@redhat.com>
2021-05-27 23:16:54 +02:00
|
|
|
[metadata]
|
|
|
|
|
name = qemu
|
python: add VERSION file
Python infrastructure as it exists today is not capable reliably of
single-sourcing a package version from a parent directory. The authors
of pip are working to correct this, but as of today this is not possible.
The problem is that when using pip to build and install a python
package, it copies files over to a temporary directory and performs its
build there. This loses access to any information in the parent
directory, including git itself.
Further, Python versions have a standard (PEP 440) that may or may not
follow QEMU's versioning. In general, it does; but naturally QEMU does
not follow PEP 440. To avoid any automatically-generated conflict, a
manual version file is preferred.
I am proposing:
- Python tooling follows the QEMU version, indirectly, but with a major
version of 0 to indicate that the API is not expected to be
stable. This would mean version 0.5.2.0, 0.5.1.1, 0.5.3.0, etc.
- In the event that a Python package needs to be updated independently
of the QEMU version, a pre-release alpha version should be preferred,
but *only* after inclusion to the qemu development or stable branches.
e.g. 0.5.2.0a1, 0.5.2.0a2, and so on should be preferred prior to
5.2.0's release.
- The Python core tooling makes absolutely no version compatibility
checks or constraints. It *may* work with releases of QEMU from the
past or future, but it is not required to.
i.e., "qemu.machine" will, for now, remain in lock-step with QEMU.
- We reserve the right to split the qemu package into independently
versioned subpackages at a later date. This might allow for us to
begin versioning QMP independently from QEMU at a later date, if
we so choose.
Implement this versioning scheme by adding a VERSION file and setting it
to 0.6.0.0a1.
Signed-off-by: John Snow <jsnow@redhat.com>
Reviewed-by: Cleber Rosa <crosa@redhat.com>
Message-id: 20210527211715.394144-12-jsnow@redhat.com
Signed-off-by: John Snow <jsnow@redhat.com>
2021-05-27 23:16:55 +02:00
|
|
|
version = file:VERSION
|
python: add qemu package installer
Add setup.cfg and setup.py, necessary for installing a package via
pip. Add a ReST document (PACKAGE.rst) explaining the basics of what
this package is for and who to contact for more information. This
document will be used as the landing page for the package on PyPI.
List the subpackages we intend to package by name instead of using
find_namespace because find_namespace will naively also packages tests,
things it finds in the dist/ folder, etc. I could not figure out how to
modify this behavior; adding allow/deny lists to setuptools kept
changing the packaged hierarchy. This works, roll with it.
I am not yet using a pyproject.toml style package manifest, because
"editable" installs are not defined (yet?) by PEP-517/518.
I consider editable installs crucial for development, though they have
(apparently) always been somewhat poorly defined.
Pip now (19.2 and later) now supports editable installs for projects
using pyproject.toml manifests, but might require the use of the
--no-use-pep517 flag, which somewhat defeats the point. Full support for
setup.py-less editable installs was not introduced until pip 21.1.1:
https://github.com/pypa/pip/pull/9547/commits/7a95720e796a5e56481c1cc20b6ce6249c50f357
For now, while the dust settles, stick with the de-facto
setup.py/setup.cfg combination supported by setuptools. It will be worth
re-evaluating this point again in the future when our supported build
platforms all ship a fairly modern pip.
Additional reading on this matter:
https://github.com/pypa/packaging-problems/issues/256
https://github.com/pypa/pip/issues/6334
https://github.com/pypa/pip/issues/6375
https://github.com/pypa/pip/issues/6434
https://github.com/pypa/pip/issues/6438
Signed-off-by: John Snow <jsnow@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Cleber Rosa <crosa@redhat.com>
Message-id: 20210527211715.394144-11-jsnow@redhat.com
Signed-off-by: John Snow <jsnow@redhat.com>
2021-05-27 23:16:54 +02:00
|
|
|
maintainer = QEMU Developer Team
|
|
|
|
|
maintainer_email = qemu-devel@nongnu.org
|
|
|
|
|
url = https://www.qemu.org/
|
|
|
|
|
download_url = https://www.qemu.org/download/
|
|
|
|
|
description = QEMU Python Build, Debug and SDK tooling.
|
|
|
|
|
long_description = file:PACKAGE.rst
|
|
|
|
|
long_description_content_type = text/x-rst
|
|
|
|
|
classifiers =
|
|
|
|
|
Development Status :: 3 - Alpha
|
|
|
|
|
License :: OSI Approved :: GNU General Public License v2 (GPLv2)
|
|
|
|
|
Natural Language :: English
|
|
|
|
|
Operating System :: OS Independent
|
|
|
|
|
Programming Language :: Python :: 3 :: Only
|
|
|
|
|
|
|
|
|
|
[options]
|
|
|
|
|
python_requires = >= 3.6
|
|
|
|
|
packages =
|
|
|
|
|
qemu.qmp
|
|
|
|
|
qemu.machine
|
|
|
|
|
qemu.utils
|
2021-05-27 23:17:00 +02:00
|
|
|
|
|
|
|
|
[pylint.messages control]
|
|
|
|
|
# Disable the message, report, category or checker with the given id(s). You
|
|
|
|
|
# can either give multiple identifiers separated by comma (,) or put this
|
|
|
|
|
# option multiple times (only on the command line, not in the configuration
|
|
|
|
|
# file where it should appear only once). You can also use "--disable=all" to
|
|
|
|
|
# disable everything first and then reenable specific checks. For example, if
|
|
|
|
|
# you want to run only the similarities checker, you can use "--disable=all
|
|
|
|
|
# --enable=similarities". If you want to run only the classes checker, but have
|
|
|
|
|
# no Warning level messages displayed, use "--disable=all --enable=classes
|
|
|
|
|
# --disable=W".
|
|
|
|
|
disable=too-many-arguments,
|
|
|
|
|
too-many-instance-attributes,
|
|
|
|
|
too-many-public-methods,
|
|
|
|
|
|
|
|
|
|
[pylint.basic]
|
|
|
|
|
# Good variable names which should always be accepted, separated by a comma.
|
|
|
|
|
good-names=i,
|
|
|
|
|
j,
|
|
|
|
|
k,
|
|
|
|
|
ex,
|
|
|
|
|
Run,
|
|
|
|
|
_,
|
|
|
|
|
fd,
|
|
|
|
|
c,
|
|
|
|
|
|
|
|
|
|
[pylint.similarities]
|
|
|
|
|
# Ignore imports when computing similarities.
|
|
|
|
|
ignore-imports=yes
|