Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #11282 > unrolled thread
| Started by | Michael Fladischer <michael@fladi.at> |
|---|---|
| First post | 2019-01-27 15:00 +0100 |
| Last post | 2019-01-27 19:50 +0100 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.debian.maint.python
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
| From | Michael Fladischer <michael@fladi.at> |
|---|---|
| Date | 2019-01-27 15:00 +0100 |
| Subject | Packaging google-cloud-python |
| Message-ID | <xkT8B-8C-7@gated-at.bofh.it> |
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 Regards, Michael
[toc] | [next] | [standalone]
| From | Scott Kitterman <debian@kitterman.com> |
|---|---|
| Date | 2019-01-27 15:40 +0100 |
| Message-ID | <xkTLj-BJ-3@gated-at.bofh.it> |
| In reply to | #11282 |
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
[toc] | [prev] | [next] | [standalone]
| From | Michael Fladischer <michael@fladi.at> |
|---|---|
| Date | 2019-01-27 19:50 +0100 |
| Message-ID | <xkXFf-2WG-5@gated-at.bofh.it> |
| In reply to | #11283 |
Hi Scott, Am 27.01.2019 um 15:36 schrieb Scott Kitterman: > Assuming you're packaging for python3 only, I don't think it's a problem: > > https://www.python.org/dev/peps/pep-0420/ thanks for this hint. I should pay more attention to PEPs. Digging deeper into the Google SDK dampened my enthusiasm quite a bit, especially the googleapis-common-protos[0] which is autogenerated using two Google internal tools "artman" and "toolbox". Nothing I would want to maintain ... [0] https://pypi.org/project/googleapis-common-protos/ Regards, Michael
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.python
csiph-web