RFS: ptex2tex (3rd try)

[Johannes Ring]

Dear mentors, debian-python,

I am looking for a sponsor for my package "ptex2tex".

* Package name: ptex2tex
 Version : 0.4-1
 Upstream Author : Hans Petter Langtangen and Ilmar Wilbers
* URL : http://ptex2tex.googlecode.com
* License : BSD-3-clause
 Section : text

It builds one binary package:
ptex2tex - easy generation of (possibly complex) LaTeX environments

The package appears to be lintian clean.

The upload would fix this bug: 641304 (ITP)

The package is available in the PAPT's Subversion repository:
- svn://svn.debian.org/python-apps/packages/ptex2tex/trunk
- http://svn.debian.org/viewsvn/python-apps/packages/ptex2tex/trunk/

I would be very happy if someone uploaded this package for me.

Kind regards,

Johannes Ring


-- 
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/CALjQY_HcVF5Z5K5Ed=km+CmnKm_0m2tH-_GEtZYhoUGa=he...@mail.gmail.com

Python: Including Nosetest

[Ole Streicher]

Dear lists,

I am working on a package (python-pywcs) that may include a "nosetest"
which I want to run before installation.

For this, I put the following line into debian/rules (for debhelper):

override_dh_auto_test:
nosetest

However, when I try to build the package, I get the error

==
ERROR: Failure: ImportError (No module named _pywcs)
--
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.7/nose/loader.py", line 390, in
loadTestsFromName
addr.filename, addr.module)
  File "/usr/lib/pymodules/python2.7/nose/importer.py", line 39, in
importFromPath
return self.importFromDir(dir_path, fqname)
  File "/usr/lib/pymodules/python2.7/nose/importer.py", line 86, in
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  File
"/home/oles/Projects/2010/launchpad-cpl/build/sid/pywcs-1.10-4.7/tests/test.py",
line 8, in 
import pywcs
  File
"/home/oles/Projects/2010/launchpad-cpl/build/sid/pywcs-1.10-4.7/lib/pywcs.py",
line 71, in 
import _pywcs
ImportError: No module named _pywcs

--

This error comes from the fact, that the nosetest uses the current
directory as the first entry in the path and so tries to read the source
directory (pywcs/...) and not the build-and-not-installed-yet version in
build/lib.linux-x86_64-2.6/ (and ...2.7). Since I assume that it is not
very clean just to include that path (or chdir there before running the
test), I guess there is another solution on how to run nosetest during
package build?

Best regards

Ole


-- 
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/4e9d4c20.6030...@liska.ath.cx

Re: Python: Including Nosetest

[Ole Streicher]

Am 18.10.2011 15:10, schrieb Yaroslav Halchenko:
> well -- if you discover some other way -- please let me know.

>From elsewhere , I got the hint
to try

 python setup.py build_ext -i

which builds the extension in-place. So my debian/rules looks like

override_dh_auto_test:
python setup.py build_ext -i && nosetests tests/test.py

This works fine for me, and I hope it will survive the review :-)

Best regards

Ole


-- 
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/4e9d8df8.4060...@liska.ath.cx

Re: Python: Including Nosetest

[Yaroslav Halchenko]

well, yeah -- but I would advise to run tests against "installed"
version of the software -- who knows what was missing from their
MANIFEST.in or setup.py files... although might require few more custom
lines, testing against installed version IMHO provides better QA.
Moreover some modules/projects even forbid (or discourage) in-source
testing (e.g. IIRC numpy)

also, depending on the setup, it might be wasting CPU while building
extensions multiple times -- first in-place, then for installation

Just my 0.1 cents

On Tue, 18 Oct 2011, Ole Streicher wrote:
>  python setup.py build_ext -i

> which builds the extension in-place. So my debian/rules looks like

> override_dh_auto_test:
>   python setup.py build_ext -i && nosetests tests/test.py

> This works fine for me, and I hope it will survive the review :-)

-- 
=--=
Keep in touch www.onerussian.com
Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic


-- 
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/20111018144710.gg10...@onerussian.com

RFS: python-pywcs

[Ole Streicher]

Dear mentors,

I am looking for a sponsor for my package "python-pywcs".

 * Package name: python-pywcs
   Version : 1.10-1
   Upstream Author : Michael Droettboom 
 * URL : https://trac6.assembla.com/astrolib
 * License : BSD
   Section : python

It builds those binary packages:

python-pywcs - Set of routines for handling the FITS WCS standard

To access further information about this package, please visit the
following URL:

  http://mentors.debian.net/package/python-pywcs

Alternatively, one can download the package with dget using this command:

  dget -x
http://mentors.debian.net/debian/pool/main/p/python-pywcs/python-pywcs_1.10-1.dsc

I would be glad if someone uploaded this package for me.

Best regards,

Ole Streicher


-- 
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/4e9db28b.7010...@liska.ath.cx

Re: Python: Including Nosetest

[Vincent Bernat]

On Tue, 18 Oct 2011 11:51:28 +0200, Ole Streicher wrote:

Dear lists,

I am working on a package (python-pywcs) that may include a 
"nosetest"

which I want to run before installation.

For this, I put the following line into debian/rules (for debhelper):

override_dh_auto_test:
nosetest


You should not run test against the source package. Instead, you should 
run tests against the yet-to-be-installed version. You need to use a 
wrapper for this. I don't know if this is the best example available but 
it works :


http://anonscm.debian.org/viewvc/python-modules/packages/cerealizer/trunk/debian/runtests.py?view=markup
http://anonscm.debian.org/viewvc/python-modules/packages/cerealizer/trunk/debian/rules?view=markup


--
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/be0749c41462c8c6bb26a5be8a2ad...@luffy.cx

Re: Python: Including Nosetest

[Ole Streicher]

Vincent Bernat  writes:
> You should not run test against the source package. Instead, you should run
> tests against the yet-to-be-installed version. 

The python package in question is a wrapper for some shared library
(wcslib).

The goal of the tests is not in the first place that they forgot
something in the manifest (things like this are usually already tested
upstream), but that the communication between the shared library, the C
wrapper and the higher level python modules. This can be tested in the
source directory as well.

Also, the place of dh_auto_test in the order of steps in dh_build
suggests at least to me as a beginner that in-place tests *before*
installation are the recommended (or at least the usual) way to go in
Debian.
Best regards

Ole


-- 
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/7548.4e9e72da.cd...@h1882623.stratoserver.net