Enhancement #1597
setup.py should specify the protobuf dependency with the exact version
| Status: | New | Start date: | 08/20/2013 | ||
|---|---|---|---|---|---|
| Priority: | Low | Due date: | |||
| Assignee: | - | % Done: | 50% | ||
| Category: | Python | ||||
| Target version: | rsb-0.18 |
Description
As the generated protocol files are coupled to a specific protobuf version, setup.py should declare the protobuf dependency explicitly with the version of protoc used to generated the protocol.
History
#1 Updated by J. Wienke over 10 years ago
- Subject changed from setup.[y should specify the protobuf dependency with the exact version to setup.py should specify the protobuf dependency with the exact version
#2 Updated by J. Wienke over 10 years ago
Hm, when thinking about this I actually don't know how to solve this ;) The dependencies are static inside the setup.py call to the setup function. We would have to do a lot of file mangling to inject the version there. Has anyone got a good idea how to solve this?
#3 Updated by J. Moringen over 10 years ago
- Target version changed from rsb-0.10 to rsb-0.11
#4 Updated by J. Wienke over 9 years ago
- Target version changed from rsb-0.11 to rsb-0.12
- % Done changed from 0 to 50
This is partially implemented for the case of compiling from source. However, this logic will not work in case of uploaded packages to pypi.
#5 Updated by J. Wienke about 9 years ago
- Target version changed from rsb-0.12 to rsb-0.13
#6 Updated by J. Moringen about 8 years ago
- Target version changed from rsb-0.13 to rsb-0.14
#7 Updated by J. Moringen almost 8 years ago
- Target version changed from rsb-0.14 to rsb-0.15
#8 Updated by J. Moringen over 7 years ago
- Target version changed from rsb-0.15 to rsb-0.16
#9 Updated by J. Moringen about 7 years ago
- Target version changed from rsb-0.16 to rsb-0.17
#10 Updated by J. Moringen over 6 years ago
- Target version changed from rsb-0.17 to rsb-0.18