Hi Barry (2013.02.22_15:38:46_+0200)
> >As discussed yesterday on IRC, nose's /usr/bin/nosetests-3.x scripts are
> >broken (provided only for python3 version(s) that was/were default on
> >build time)
>
> Sorry, can you please provide more detail for folks who were not participating
> in the IRC discussion? Is there no better way to provide nosetests-X.Y
> scripts with the proper shebang lines for all supported Python versions?
Our options were:
1. Status quo: Provide a nosetests-3.X script for the default version at
build time.
Pros: None
Cons:
- This potentially breaks unit tests if there are two supported 3.x
versions.
2. Drop all nosetsts-3.X scripts.
Pros:
- Maintainers who were aware of the problems with 1 had to manually
call python3.X /usr/bin/nostests3 anyway, so this doesn't cause
them any harm.
- Don't accidentally end up with dependencies on all python3.Xs
Cons:
- Maintainers who weren't needed their packages patched.
3. Apply a messy patch to generate scripts based on py3verions -s at
build time.
Pros:
- Neat
Cons:
- It's ugly as hell
- Have to do a sourceful upload for each python3 supported versions
change
- Will accidentally end up with dependencies on all python3.Xs
4. Use .rtinstall, .rtremove, postinst, and prerm scripts to maintain
all the nosetsets-3.X scripts (pytest does this)
Pros:
- Neat
- No accidental dependencies on all python3.Xs
Cons:
- You are creating and deleting things in /usr/bin in maintainer
scripts - this made some people cringe.
2 seemed better than 1, and was dead easy.
Given the fairly low number of packages using python3-nose, fixing them
wasn't hard.
SR
--
Stefano Rivera
http://tumbleweed.org.za/
H: +27 21 461 1230 C: +27 72 419 8559
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130222215103.gb29...@bach.rivera.co.za
