Pending broken links

Hello, I have noticed that the automatically generated links sent to the BTS on git changes that close bugs are broken. e.g. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855510#10 has the following link: http://git.debian.org/?p=python-modules/packages/slimit.git;a=commitdiff;h=d20c791

Re: Implicit namespace packages (was: Re: How to split modules in multiple deb packages)

> > This is not a Python package. > > > > (Hint: no __init__.py…) > > Not required for Python3. > > https://www.python.org/dev/peps/pep-0420/ Yep, you're right. But that would still have to be declared in __init__.py to work properly, right? If not, that would be cool… -nik --

Re: How to split modules in multiple deb packages

Hi, > > Well, in that case, with you being upstream, I'd separate the two > > packages entirely. > > Yes, I can do that. But, don't you think a whole package for a single > python file is... too much? Well, is it? You were the one asking how to split it ;)… So, if you think the RPi and non-RPi

Re: How to split modules in multiple deb packages

Hi Dominik, thanks for your reply. > Well, in that case, with you being upstream, I'd separate the two > packages entirely. Yes, I can do that. But, don't you think a whole package for a single python file is... too much? >> I can exclude rpi.py module from main package and create a >>

Re: How to split modules in multiple deb packages

Dominik George writes: > This is not a Python package. > > (Hint: no __init__.py…) Not required for Python3. https://www.python.org/dev/peps/pep-0420/ -- Brian May

Re: How to split modules in multiple deb packages

Hi, > Hello everybody, I'm packaging a daemon that I've developed in python3 and I > need to split the core modules in two deb packages, but I don't now how to do > that. > > One of the module is specific for Raspberry Pi, it adds some > functionalities, but > the daemon itself doesn't require a