Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #11283
| From | Scott Kitterman <debian@kitterman.com> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Packaging google-cloud-python |
| Date | 2019-01-27 15:40 +0100 |
| Message-ID | <xkTLj-BJ-3@gated-at.bofh.it> (permalink) |
| References | <xkT8B-8C-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Packaging google-cloud-python Michael Fladischer <michael@fladi.at> - 2019-01-27 15:00 +0100
Re: Packaging google-cloud-python Scott Kitterman <debian@kitterman.com> - 2019-01-27 15:40 +0100
Re: Packaging google-cloud-python Michael Fladischer <michael@fladi.at> - 2019-01-27 19:50 +0100
csiph-web