-
Notifications
You must be signed in to change notification settings - Fork 573
chore: use uv for version #1160
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
Conversation
| current = io.open(os.path.join(os.path.dirname('__file__'), 'appium', 'version.py'), encoding='utf-8').read().rstrip() | ||
| print('The current version is {}, type a new one'.format(MESSAGE_YELLOW.format(current))) | ||
| return current | ||
| os.system('uv version') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this method does not return anything, but looks like it should
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The original one was also to print the version in the stdout, so return value is not matter
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
then the method name is confusing as get prefix implicitly assumes it must return something
|
-> I think we can use #1161 after initial release with |
uv versioncan be used to manage versions. The getting version code has references, so this PR keeps the version file to returnimportlib.metadata.version('Appium-Python-Client'). It is available since Python v3.8, and we require Python v3.9+ so should be ok.