Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recommend consistent method for getting package version in python #336

Closed
wjwwood opened this issue Jan 28, 2013 · 1 comment
Closed

Recommend consistent method for getting package version in python #336

wjwwood opened this issue Jan 28, 2013 · 1 comment

Comments

@wjwwood
Copy link
Member

wjwwood commented Jan 28, 2013

In catkin packages the version is defined in the package.xml, and we should provide a mechanism for getting the current version in python (and perhaps C++), such that there is no duplication of the version number required.

This would be used, for example, by the catkin_* tools so that they can know the version of catkin being used at run time. See #331

This should work in install/devel space and probably source space (catkin_make is called before catkin has had cmake called). Additionally, it should pick the correct version in an overlay situation.

@dirk-thomas dirk-thomas changed the title Provide consistent method for getting package version in python Recommend consistent method for getting package version in python Apr 4, 2014
@dirk-thomas
Copy link
Member

Since this is unlikely to be addressed I will close this ticket.

Currently the information from the manifest can either be accessed by parsing the manifest or in order to avoid that overhead the version number can be duplicated in the Python code.

@dirk-thomas dirk-thomas removed this from the untargeted milestone Jan 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants