[Bug 755139] Review Request: python-nose1.1 - Discovery-based unittest extension for Python

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


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

--- Comment #10 from Toshio Ernie Kuratomi <a.badger at gmail.com> 2011-11-21 12:27:59 EST ---
(In reply to comment #7)
> Will this spec create python3-nose rather than python3-nose1.1 ?

I haven't tested (no python3 package yet on RHEL6) but the spec should do the
right thing or error out:

# In %install
rm %{buildroot}%{_bindir}/nosetests
[..]
mv %{buildroot}%{_bindir}/nosetests-%{python3_version}
%{buildroot}%{_bindir}/nosetests%{maj_ver}-%{python3_version}

# In %files
%{_bindir}/nosetests%{maj_ver}-%{python3_version}

Note, the reason that this isn't installed as python3-nosetests%{maj_ver} is
that upstream chose to install the python3 script as
nosetests-%{python3_version}.  So to maintain consistency with any
documentation that upstream generates around this, I stuck with a name that is
easy to find via tab completion/etc.

(In reply to comment #8)
> Also for my own reference, I think it would be good if rebasing python-nose in
> RHEL, that both that and this package Provide: python-nose1
> (Note that python-nose-1.0 is enough to build sqlalchemy at least)
> 
I'm loath to do that as python-nose-1.1 has incompatible API changes with
python-nose-1.0.  So some things can use either package but other things would
break.

> That would allow dependent packages to require just python-nose1
> and not need to install the actual python-nose1.1 compat package too.
> The rebased package would also need to Conflicts: python-nose1.1
> as the eggs would overlap.

The problem with trying to specify what the RHEL package should do is that we
have no control over it.  If RHEL were to rebase its nose packages, the right
thing would be for it to rebase to 1.1 (as rebasing to 1.0 would also break API
compat, they might as well take on the most recent version).  If they do that,
they should add an Obsoletes and Provides with python-nose1.1 and we should
remove the python-nose1.1 package from EPEL at that time.

Note that the python-nose package will probably not need a Conflicts in any
case -- since nose uses distutils rather than setuptools, its egg-info will use
a different name and format than this package:

compat package installed via easy_install:
  /usr/lib/python2.6/site-packages/nose-1.1.2-py2.6.egg
standard nose installed with distutils:
  /usr/lib/python2.6/site-packages/nose-1.1.2-py2.6.egg-info

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.