➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2017-03-09 16:25 by paul.moore, last changed 2022-04-11 14:58 by admin. This issue is now closed.
| Messages (2) | |||
|---|---|---|---|
| msg289305 - (view) | Author: Paul Moore (paul.moore) *  |
Date: 2017-03-09 16:25 | |
The 3.6.1rc1 build seems to have a spurious "^0" at the end of the version, before the VCS ID - 3.6.1rc1^0): >py -3.6 Python 3.6.1rc1 (v3.6.1rc1^0:e0fbe5feee4f9c00f09eb9659c2182183036261a, Mar 4 2017, 20:00:12) [MSC v.1900 64 bit (AMD64)] on win32 >>> sys.version '3.6.1rc1 (v3.6.1rc1^0:e0fbe5feee4f9c00f09eb9659c2182183036261a, Mar 4 2017, 20:00:12) [MSC v.1900 64 bit (AMD64)]' It's not showing in sys.version_info, so it's probably only cosmetic. Also, I don't think this is really a release blocker - just marking it as such so it gets checked (I wonder if it's an artifact of the github migration, I think git uses ^0 to mean something specific in relation to commit IDs?) I've only checked on Windows. I don't know if it's the same on Unix. If it's deemed cosmetic, I'm happy for it to be downgraded to non-blocking, or even closed as not an issue. Just wanted to flag it up in case it's a symptom of something deeper. |
|||
| msg289326 - (view) | Author: Ned Deily (ned.deily) * |
Date: 2017-03-09 20:14 | |
Thanks, Paul, we are aware of the spurious ^0. It will be resolved under Issue 25793. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:58:44 | admin | set | github: 73961 |
| 2017-03-09 20:14:57 | ned.deily | set | status: open -> closed priority: release blocker -> resolution: duplicate messages: + msg289326 superseder: Deprecate sys._mercurial and create sys._git stage: resolved |
| 2017-03-09 16:25:23 | paul.moore | create | |