#962 Docuemnt how to pass arguments to %py3_build/install
Merged by churchyard. Opened by churchyard.
churchyard/packaging-committee py_args  into  master

Download 962.patch

https://bugzilla.redhat.com/show_bug.cgi?id=1818920

I find this confusing; it could use an example.
AFAIK the only real-world use case we know so far is for install, so I'd say something like this for install:

Various flags are passed to `+setup.py install+`, see `/usr/lib/rpm/macros.d/macros.python3` for details and similar macros.
To add extra flags/arguments to `+setup.py install+`, separate them with `+--+`, for example: `%py3_install -- --install-scripts %{_libexecdir}`.
To pass custom command line arguments directly to `+setup.py+`, define `+%py_setup_args+`.

and refer to that from build.

That makes sense.

rebased onto b4832d9db8fffae25d868dd671896eae65f0f44b

Amended.

Yes, that's what I had in mind.

rebased onto dab3ce5bb7e77a0b3eedb65ab3bd1e738802a174

Metadata Update from @churchyard:
- Pull-request tagged with: meeting

Since this doesn't really change the guidelines, only documentation, I'm merging it.

rebased onto 856119691300fc961c19b1895ebb7caf8a8cd64c

Pull-Request has been merged by churchyard

Metadata