Python guidelines cleanup

Jason L Tibbitts III tibbs at math.uh.edu
Thu Jul 30 16:23:29 UTC 2015


>>>>> "MH" == Miro HronĨok <mhroncok at redhat.com> writes:

MH>  * in example spec, you mix srcname and pypi_name macros

Yeah, fixed that up.

MH>  * For example, the python 3 version of "coverage" must ship
MH>    executables
MH> /usr/bin/coverage, /usr/bin/coverage-2 and /usr/bin/coverage-2.7,
MH> while the python 3 version must provide /usr/bin/coverage-3 and
MH> /usr/bin/coverage-3.4 (assuming python3 is Python 3.4).

That was just copied over as far as I know, but I've fixed it up in my
draft.  Good that this is resulting in some bug fixing.

MH>  * Must: If you build for a single python runtime you must add
MH> %python_provide python-$module so that the current default python is
MH> provided from the unversioned python package.

MH> I'm quite confused with this and don't understand it all. Generally
MH> %python_provide is not explained at all... ?

I need to get with tomspur and bang out documentation for the new
macros, which will go at the beginning of the document.

 - J<


More information about the python-devel mailing list