Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #10401 > unrolled thread

Several questions regarding package tifffile

Back to article view | Back to linux.debian.maint.python

Contents

  Several questions regarding package tifffile Andreas Tille <andreas@an3as.eu> - 2018-04-09 09:50 +0200
    Re: Several questions regarding package tifffile Andrey Rahmatullin <wrar@debian.org> - 2018-04-09 10:20 +0200
      Re: Several questions regarding package tifffile Andrey Rahmatullin <wrar@debian.org> - 2018-04-09 13:10 +0200
      Re: Several questions regarding package tifffile Andreas Tille <andreas@an3as.eu> - 2018-04-09 13:10 +0200
    Re: Several questions regarding package tifffile Ghislain Vaillant <ghisvail@gmail.com> - 2018-04-09 10:40 +0200
      Re: Several questions regarding package tifffile Piotr Ożarowski <piotr@debian.org> - 2018-04-09 11:00 +0200
      Re: Several questions regarding package tifffile Andreas Tille <andreas@fam-tille.de> - 2018-04-09 12:10 +0200
      Re: Several questions regarding package tifffile Andreas Tille <andreas@an3as.eu> - 2018-05-22 15:10 +0200

#10401 — Several questions regarding package tifffile

Hi,

I realised that upstream of tifffile[1] switched to Python3.  When
inspecting the package I somehow think that its main purpose is rather a
user application than a Python module and thus I would rather rename the
binary from python-tifffile to tifffile than python3-tifffile.  What do
you think?

As per [2] I added dh-python to the Build-Depends but it seems I would
need python-minimal in addition to get /usr/bin/pyversions.  For me it
is a bit strange to realise that this basic functionality is not provided
by dh-python "Depends: python-minimal".  Am I missing something?

It also seems that a Build-Depends: python3-distutils and if I add it it
tries to do "python setup.py clean -a" which is stupid since there is no
setup.py (and also no python but only python3).  I wonder whether I'm
missing something here as well in this very simple package which does
not seem to work well with dh-python.

BTW, I'd be *really* happy if somebody from Python team would take over
this package into Python packaging team.  I just adopted it from a
former Debian Med team member but it is not Debian Med specific at all
and I have no real interest in this package.

Kind regards

       Andreas.

PS: Please CC me, I'm not subscribed to this list.

[1] https://salsa.debian.org/med-team/tifffile
[2] https://people.debian.org/~piotr/dh_python2_without_dh-python.ddlist

-- 
http://fam-tille.de

[toc] | [next] | [standalone]

#10402

[Multipart message — attachments visible in raw view] — view raw

On Mon, Apr 09, 2018 at 09:45:52AM +0200, Andreas Tille wrote:
> As per [2] I added dh-python to the Build-Depends but it seems I would
> need python-minimal in addition to get /usr/bin/pyversions.  For me it
> is a bit strange to realise that this basic functionality is not provided
> by dh-python "Depends: python-minimal".  Am I missing something?
python-minimal is 2.x, you don't need it.
As the auto-detected python_distutils system assumes python2 you need to
move to pybuild or manual setup.py calls.

> It also seems that a Build-Depends: python3-distutils and if I add it it
> tries to do "python setup.py clean -a" which is stupid since there is no
> setup.py
Wrong: debian/patches/setuppy.patch adds it.

-- 
WBR, wRAR

[toc] | [prev] | [next] | [standalone]

#10406

[Multipart message — attachments visible in raw view] — view raw

On Mon, Apr 09, 2018 at 01:01:20PM +0200, Andreas Tille wrote:
> > > As per [2] I added dh-python to the Build-Depends but it seems I would
> > > need python-minimal in addition to get /usr/bin/pyversions.  For me it
> > > is a bit strange to realise that this basic functionality is not provided
> > > by dh-python "Depends: python-minimal".  Am I missing something?
> > python-minimal is 2.x, you don't need it.
> > As the auto-detected python_distutils system assumes python2 you need to
> > move to pybuild or manual setup.py calls.
> > 
> > > It also seems that a Build-Depends: python3-distutils and if I add it it
> > > tries to do "python setup.py clean -a" which is stupid since there is no
> > > setup.py
> > Wrong: debian/patches/setuppy.patch adds it.
> 
> Ahhhh, thanks for opening my eyes. ;-)
> 
> May be the clue is to make this python3-ish ...
I'd expect it to already support python3, you just need to change d/rules.

-- 
WBR, wRAR

[toc] | [prev] | [next] | [standalone]

#10407

Hi,

On Mon, Apr 09, 2018 at 01:09:55PM +0500, Andrey Rahmatullin wrote:
> On Mon, Apr 09, 2018 at 09:45:52AM +0200, Andreas Tille wrote:
> > As per [2] I added dh-python to the Build-Depends but it seems I would
> > need python-minimal in addition to get /usr/bin/pyversions.  For me it
> > is a bit strange to realise that this basic functionality is not provided
> > by dh-python "Depends: python-minimal".  Am I missing something?
> python-minimal is 2.x, you don't need it.
> As the auto-detected python_distutils system assumes python2 you need to
> move to pybuild or manual setup.py calls.
> 
> > It also seems that a Build-Depends: python3-distutils and if I add it it
> > tries to do "python setup.py clean -a" which is stupid since there is no
> > setup.py
> Wrong: debian/patches/setuppy.patch adds it.

Ahhhh, thanks for opening my eyes. ;-)

May be the clue is to make this python3-ish ...

On the other hand, this might mean that the original packager Mathieu
Malaterre intentionally had created a module.  Mathieu, can you please
enlighten us about your intention?  The package has a few users
according to popcon but my capacity to keep your leftovers alife is
limited and without some clear statement about your packaging intentions
it is a bit hard to do a sensible Python3 move.

Kind regards

        Andreas.

-- 
http://fam-tille.de

[toc] | [prev] | [next] | [standalone]

#10403

[Multipart message — attachments visible in raw view] — view raw

Le lun. 9 avr. 2018 à 08:46, Andreas Tille <andreas@an3as.eu> a écrit :

> Hi,
>
> I realised that upstream of tifffile[1] switched to Python3.  When
> inspecting the package I somehow think that its main purpose is rather a
> user application than a Python module and thus I would rather rename the
> binary from python-tifffile to tifffile than python3-tifffile.  What do
> you think?
>
> As per [2] I added dh-python to the Build-Depends but it seems I would
> need python-minimal in addition to get /usr/bin/pyversions.  For me it
> is a bit strange to realise that this basic functionality is not provided
> by dh-python "Depends: python-minimal".  Am I missing something?
>
> It also seems that a Build-Depends: python3-distutils and if I add it it
> tries to do "python setup.py clean -a" which is stupid since there is no
> setup.py (and also no python but only python3).  I wonder whether I'm
> missing something here as well in this very simple package which does
> not seem to work well with dh-python.
>
> BTW, I'd be *really* happy if somebody from Python team would take over
> this package into Python packaging team.  I just adopted it from a
> former Debian Med team member but it is not Debian Med specific at all
> and I have no real interest in this package.
>

I could have a look at it. Do you reckon why the package was needed
originally? I am surprised it landed in d-med, so perhaps there is another
package needing it?


> Kind regards
>
>        Andreas.
>
> PS: Please CC me, I'm not subscribed to this list.
>
> [1] https://salsa.debian.org/med-team/tifffile
> [2] https://people.debian.org/~piotr/dh_python2_without_dh-python.ddlist
>
> --
> http://fam-tille.d <http://fam-tille.de>e
>

Cheers,
Ghis

>

[toc] | [prev] | [next] | [standalone]

#10404

[Ghislain Vaillant, 2018-04-09]
> > I realised that upstream of tifffile[1] switched to Python3.  When
> > inspecting the package I somehow think that its main purpose is rather a
> > user application than a Python module and thus I would rather rename the
> > binary from python-tifffile to tifffile than python3-tifffile.  What do
> > you think?

please also move the module to private dir by passing this option to
setup.py:

  --install-lib=/usr/lib/tifffile

or if you decide to use pybuild:

  export PYBUILD_INSTALL_ARGS=--install-lib=/usr/lib/tifffile


if you don't want to mess with PYTHONPATH, install script there as well
(--install-scripts=/usr/lib/tifffile) and symlink /usr/bin/foo to
/usr/lib/tifffile/yourscript
-- 
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645

[toc] | [prev] | [next] | [standalone]

#10405

On Mon, Apr 09, 2018 at 08:39:00AM +0000, Ghislain Vaillant wrote:
> 
> I could have a look at it. Do you reckon why the package was needed
> originally? I am surprised it landed in d-med, so perhaps there is another
> package needing it?

$ apt-cache rdepends python-tifffile
python-tifffile
Reverse Depends:
  med-imaging
  med-imaging-dev

The former maintainer has just put it in Debian Med without any
explanation.  It is also mentioned in the med-imaging tasks but no
other dependant packages I'm aware of.

Kind regards

       Andreas.

-- 
http://fam-tille.de

[toc] | [prev] | [next] | [standalone]

#10574

Hi Ghislain,

On Mon, Apr 09, 2018 at 08:39:00AM +0000, Ghislain Vaillant wrote:
> Le lun. 9 avr. 2018 à 08:46, Andreas Tille <andreas@an3as.eu> a écrit :
> 
> > I realised that upstream of tifffile[1] switched to Python3.  When
> > inspecting the package I somehow think that its main purpose is rather a
> > user application than a Python module and thus I would rather rename the
> > binary from python-tifffile to tifffile than python3-tifffile.  What do
> > you think?
> >
> > As per [2] I added dh-python to the Build-Depends but it seems I would
> > need python-minimal in addition to get /usr/bin/pyversions.  For me it
> > is a bit strange to realise that this basic functionality is not provided
> > by dh-python "Depends: python-minimal".  Am I missing something?
> >
> > It also seems that a Build-Depends: python3-distutils and if I add it it
> > tries to do "python setup.py clean -a" which is stupid since there is no
> > setup.py (and also no python but only python3).  I wonder whether I'm
> > missing something here as well in this very simple package which does
> > not seem to work well with dh-python.
> >
> > BTW, I'd be *really* happy if somebody from Python team would take over
> > this package into Python packaging team.  I just adopted it from a
> > former Debian Med team member but it is not Debian Med specific at all
> > and I have no real interest in this package.
> >
> 
> I could have a look at it.

Did you manage to do this?

> Do you reckon why the package was needed
> originally? I am surprised it landed in d-med, so perhaps there is another
> package needing it?

No idea.  It was started by Mathieu Malaterre who left the team.  Feel
free to move to DPMT.

Kind regards

       Andreas.


-- 
http://fam-tille.de

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web