Path: csiph.com!news.redatomik.org!aioe.org!bofh.it!news.nic.it!robomod
From: Scott Kitterman <debian@kitterman.com>
Newsgroups: linux.debian.maint.python
Subject: Re: Packaging google-cloud-python
Date: Sun, 27 Jan 2019 15:40:01 +0100
Message-ID: <xkTLj-BJ-3@gated-at.bofh.it>
References: <xkT8B-8C-7@gated-at.bofh.it>
Old-Return-Path: <debian@kitterman.com>
User-Agent: KMail/4.13.3 (Linux/3.13.0-164-generic; KDE/4.13.3; x86_64; ; )
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Approved: robomod@news.nic.it
Lines: 22
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:11283

On Sunday, January 27, 2019 02:34:28 PM Michael Fladischer wrote:
> Hi,
> 
> I'd like to package several client modules from the google-cloud-python
> repo[0]. The problem ist, each client module includes google/__init__.py
> and google/cloud/__init__.py, so installing two ore more of these
> modules would cause conflicts.
> My idea to tackle this was to introduce some sort of base package that
> just includes those two files and have all the individual client
> packages depend on this one.
> This brings me to the next problem: Upstream does not provide such a
> base package. Would it be acceptable to make a debian-only base package
> with no upstream, pulling those to files from one of the upstream packages?
> Or are there any other options?
> 
> [0] https://github.com/googleapis/google-cloud-python

Assuming you're packaging for python3 only, I don't think it's a problem:

https://www.python.org/dev/peps/pep-0420/

Scott K