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

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

Extra debian.blends Python package

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

Contents

  Extra debian.blends Python package Ole Streicher <olebole@debian.org> - 2018-03-24 11:00 +0100
    Re: Extra debian.blends Python package Piotr Ożarowski <piotr@debian.org> - 2018-03-26 23:40 +0200

#10302 — Extra debian.blends Python package

Hi,

I am currently rewriting part of the blends-dev package which is used
for maintaining Debian Pure Blends into Python. This however comes out
some abstractions of Blends (namely the tasks infrastructure) that may
be re-usable on other places, f.e. in the blends.d.o web service. So it
is probably a good idea to create a separate Python package from it.

Since this package deals with tasks sources, it sounds natural to put
this as a sub-package of the "debian" package. I would however not like
to integrate the sources to python-debian. First, it is very new and
likely to change API quickly in the next time. But also, the blends
subpackage is quite special; there is no need to have it installed in
such a broad manner as python-debian.

And finally, I do not care about Python 2 compatibility here.

What I could do easily is to create a python3-debian-blends binary
package (maintained in the "blends" source package) for this subpackage,
just installs a "blends.py" into ../dist-packages/debian/

Since this is however somehow hijacking (part of) the namespace of
python-debian, I'd like to know the policy here.

Are there any problems with that approach?

Best regards

Ole

[toc] | [next] | [standalone]

#10337

[Ole Streicher, 2018-03-24]
> I am currently rewriting part of the blends-dev package which is used
> for maintaining Debian Pure Blends into Python. This however comes out
> some abstractions of Blends (namely the tasks infrastructure) that may
> be re-usable on other places, f.e. in the blends.d.o web service. So it
> is probably a good idea to create a separate Python package from it.
> 
> Since this package deals with tasks sources, it sounds natural to put
> this as a sub-package of the "debian" package. I would however not like
> to integrate the sources to python-debian. First, it is very new and
> likely to change API quickly in the next time. But also, the blends
> subpackage is quite special; there is no need to have it installed in
> such a broad manner as python-debian.
> 
> And finally, I do not care about Python 2 compatibility here.
> 
> What I could do easily is to create a python3-debian-blends binary

python3-debian-blends suggests some kind of addon ("-", not ".") to
"debian" module. 

Will this package provide a public module? If so python-modulename is
your name, if not - why can't you re-use "blends" namespace? (blends-python3?)

> package (maintained in the "blends" source package) for this subpackage,
> just installs a "blends.py" into ../dist-packages/debian/

ah, so python3-debian.blends is the name. I'd talk with python3-debian
maintainers about including it in the python3-debian, though
-- 
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645

[toc] | [prev] | [standalone]

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

csiph-web