> "PV" == Petr Viktorin writes:
PV> No, getting. Example expansion:
PV> %{python_dist_name ndg_HTTPSclient} => ndg-httpsclient
Ah, OK, that makes much more sense.
PV> Would "python3_requires" and "python3_buildrequires" be better?
I think so.
PV> Please do and share your thoughts, I trust
On 08/10/2016 06:49 PM, Jason L Tibbitts III wrote:
"PV" == Petr Viktorin writes:
PV> * One macro for getting the canonical (normalized) dist-name:
PV> %{python_dist_name NAME}
Do you mean "setting" here?
No, getting. Example expansion:
%{python_dist_name ndg_HTTPSclient} => ndg-httpscl
Is an unversioned python(name) also being created automagically? I manually
create these for the command line tools which support multiple Python
versions, where the python2-name and python3-name package both provide
python(name) and then the name package requires python(name) with a
recommends for
> "PV" == Petr Viktorin writes:
PV> * One macro for getting the canonical (normalized) dist-name:
PV> %{python_dist_name NAME}
Do you mean "setting" here?
PV> * Four macros for adding Requires and BuildRequires lines (which use
PV> the python_dist_name macro above):
PV> %{requires
To help automatic building RPMs from native Python packages, we need an
automatic way to record the software's upstream name (dist name, name
on PyPI) in Fedora packages.
For this, we are using RPM's automatic dependency generator written by
Per Øyvind Karlsen and Neal Gompa, which automatically
Ok problem solved by upstream developer :-)
Here the package review request that I have just filled
python-django-model-utils - Django model mixins and utilities -
https://bugzilla.redhat.com/1365782
___
python-devel mailing list
python-devel@lists.fedora
On 08/10/2016 06:55 AM, William Moreno wrote:
Hello, due to lack of time I'm orphaning the package nsnake
Is nsnake related to Python? Maybe you wanted to send this to
fedora-devel rather than python-devel?
--
Petr Viktorin
___
python-devel mailin
