Hi Ioannes,
> why would you want to do that?
> i mean: what harm comes from shipping the rpi.py file on non-rpi systems?
Because only the rpi module requires gpiozero module to work properly,
but I cannot put a dependency on gpiozero for the whole package.
> is that file exposed to the user or i
[Simone Rossetto, 2017-02-21]
> > ("mypackage" is module name which will be shipped in python3-mypackage
> > binary package and "rpi" or "rpi-daemon" is binary package shipping the
> > daemon)
> > [...]
> > if it's one file only (without private modules) you can install directly
> > into /usr/bin/
Hi Piotr,
> ("mypackage" is module name which will be shipped in python3-mypackage
> binary package and "rpi" or "rpi-daemon" is binary package shipping the
> daemon)
> [...]
> if it's one file only (without private modules) you can install directly
> into /usr/bin/
The file rpi.py is a module o
On 2017-02-18 09:16, Simone Rossetto wrote:
> One of the module is specific for Raspberry Pi, it adds some
> functionalities, but
> the daemon itself doesn't require a Pi hardware and can still do its job
> without that module even on a Pi. What I want to do is to split the modules
> in two deb pac
[Simone Rossetto, 2017-02-18]
> 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 i
> > 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
--
PGP-Fingerprint
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
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
>> python3-m
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
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
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 Pi hardware and can
11 matches
Mail list logo