Re: Idea: pynose as drop-in replacement for nose

[Miro Hrončok]

On 09. 04. 24 19:30, Sandro wrote:
>  Therefore, I'm thinking of introducing pynose as a drop in
> replacement of 
>  deprecated nose. Pynose uses the same namespace as nose, but provides 
>  python3dist(pynose). Thus adding Provides: for nose would make it a drop-in 
>  replacement for packages currently depending on nose. 
FTR We MUST NOT add RPM Provides for python3dist(nose) unless we package nose 
dist-info metadata.

For example %pyproject_buildrequires queries Python for installed packages 
(hence it reads the packaged dist-info/egg-info metadata) and it will see nose 
is not installed.

It will then query dnf to install python3dist(nose). dnf will install pynose.

%pyproject_buildrequires will see nose is not installed. It will query dnf to 
install python3dist(nose) again. dnf will install nothing.

The %pyproject_buildrequires phase will end prematurely when dnf installs nothing.

-- 
Miro Hrončok
-- 
Phone: [phone]
IRC: mhroncok