-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Tornado version and version_info inconsistent #3406
Comments
Oops. I was just thinking that this part of the release process was too manual. ;-) How do you use these fields? Is there a good reason to fix it quickly or is it just something to get right next time? |
The fields are used for verification. It's something that can be fixed next
time. We can use the version variable in place of version_info.
…On Tue, Jun 18, 2024, 21:41 Ben Darnell ***@***.***> wrote:
Oops. I was just thinking that this part of the release process was too
manual. ;-) How do you use these fields? Is there a good reason to fix it
quickly or is it just something to get right next time?
—
Reply to this email directly, view it on GitHub
<#3406 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEW5KSF6HLX4VNXJF4B7YWTZIDOWDAVCNFSM6AAAAABJOKDG3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZXGM3DCNJYHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
bdarnell
added a commit
to bdarnell/tornado
that referenced
this issue
Jun 28, 2024
These two values should always match, but they're updated manually so test to catch mistakes. Closes tornadoweb#3406
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The reported version is 6.4.1 however version_info is reported as (6,4,0,1). This is not consistent with how the version is reported in previous releases.
The text was updated successfully, but these errors were encountered: