mirror of
https://github.com/Motorhead1991/qemu.git
synced 2025-07-28 21:03:54 -06:00
python: add Makefile for some common tasks
Add "make venv" to create the pipenv-managed virtual environment that contains our explicitly pinned dependencies. Add "make check" to run the python linters [in the host execution environment]. Add "make venv-check" which combines the above two: create/update the venv, then run the linters in that explicitly managed environment. Add "make develop" which canonizes the runes needed to get both the linting pre-requisites (the "[devel]" part), and the editable live-install (the "-e" part) of these python libraries. make clean: delete miscellaneous python packaging output possibly created by pipenv, pip, or other python packaging utilities make distclean: delete the above, the .venv, and the editable "qemu" package forwarder (qemu.egg-info) if there is one. Signed-off-by: John Snow <jsnow@redhat.com> Reviewed-by: Cleber Rosa <crosa@redhat.com> Tested-by: Cleber Rosa <crosa@redhat.com> Message-id: 20210527211715.394144-29-jsnow@redhat.com Signed-off-by: John Snow <jsnow@redhat.com>
This commit is contained in:
parent
31622b2a8a
commit
6560379fac
3 changed files with 55 additions and 0 deletions
|
@ -28,6 +28,9 @@ Installing ".[devel]" instead of "." will additionally pull in required
|
|||
packages for testing this package. They are not runtime requirements,
|
||||
and are not needed to simply use these libraries.
|
||||
|
||||
Running ``make develop`` will pull in all testing dependencies and
|
||||
install QEMU in editable mode to the current environment.
|
||||
|
||||
See `Installing packages using pip and virtual environments
|
||||
<https://packaging.python.org/guides/installing-using-pip-and-virtual-environments/>`_
|
||||
for more information.
|
||||
|
@ -39,6 +42,9 @@ Files in this directory
|
|||
- ``qemu/`` Python package source directory.
|
||||
- ``tests/`` Python package tests directory.
|
||||
- ``avocado.cfg`` Configuration for the Avocado test-runner.
|
||||
Used by ``make check`` et al.
|
||||
- ``Makefile`` provides some common testing/installation invocations.
|
||||
Try ``make help`` to see available targets.
|
||||
- ``MANIFEST.in`` is read by python setuptools, it specifies additional files
|
||||
that should be included by a source distribution.
|
||||
- ``PACKAGE.rst`` is used as the README file that is visible on PyPI.org.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue