bpy.app.version and bpy.data.version are reporting different version numbers from Python interactive console #77489

New Issue

Mikeycal Meyers · 2020-06-06T07:38:18+02:00

Mikeycal Meyers commented

2020-06-06 07:38:18 +02:00

System Information
Operating system: Linux-5.4.0-33-generic-x86_64-with-debian-bullseye-sid 64 Bits
Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64

Blender Version
Broken: version: 2.83.0, branch: master, commit date: 2020-06-03 14:38, hash: 211b6c29f7
Works: in 2.82b and all other previous versions I have tested.

Short description of error
bpy.app.version- [x] (version of blender) and bpy.data.version- [x](blend file version) are reporting different numbers when they have always been identical.

Exact steps for others to reproduce the error

Open Python console in blender and execute:

bpy.app.version
and
bpy.data.version

**System Information** Operating system: Linux-5.4.0-33-generic-x86_64-with-debian-bullseye-sid 64 Bits Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64 **Blender Version** Broken: version: 2.83.0, branch: master, commit date: 2020-06-03 14:38, hash: `211b6c29f7` Works: in 2.82b and all other previous versions I have tested. **Short description of error** bpy.app.version- [x] (version of blender) and bpy.data.version- [x](blend file version) are reporting different numbers when they have always been identical. **Exact steps for others to reproduce the error** Open Python console in blender and execute: bpy.app.version and bpy.data.version

Mikeycal Meyers commented

2020-06-06 07:38:18 +02:00

Added subscriber: @mikeycal

blender-admin commented

2020-06-06 07:38:18 +02:00

#78090 was marked as duplicate of this issue

Ankit Meel commented

2020-06-06 09:15:25 +02:00

Added subscriber: @ankitm

Ankit Meel commented

2020-06-06 09:15:25 +02:00

Blender version numbers changed to standard MAJOR.MINOR.PATCH format. Most scripts will continue to work without changes.
- bpy.app.version now returns (MAJOR, MINOR, PATCH). The PATCH version is 0 for the first stable release and increases for every bugfix release. Sub-version numbers or letters are no longer used.
- bpy.app.version_string now includes Alpha or Beta for releases under development, for example 2.90 Alpha.
..

https://wiki.blender.org/wiki/Reference/Release_Notes/2.83/Python_API

``` Blender version numbers changed to standard MAJOR.MINOR.PATCH format. Most scripts will continue to work without changes. - bpy.app.version now returns (MAJOR, MINOR, PATCH). The PATCH version is 0 for the first stable release and increases for every bugfix release. Sub-version numbers or letters are no longer used. - bpy.app.version_string now includes Alpha or Beta for releases under development, for example 2.90 Alpha. .. ``` https://wiki.blender.org/wiki/Reference/Release_Notes/2.83/Python_API

Evan Wilson commented

2020-06-07 01:07:21 +02:00

Added subscriber: @EAW

Evan Wilson commented

2020-06-07 01:07:21 +02:00

Changed status from 'Needs Triage' to: 'Archived'

Evan Wilson closed this issue

2020-06-07 01:07:21 +02:00

Evan Wilson self-assigned this 2020-06-07 01:07:21 +02:00

Evan Wilson commented

2020-06-07 01:07:21 +02:00

Thank you for the report. As noted above, this is a documented design change, and not a bug.

Evan Wilson commented

2020-06-21 22:17:48 +02:00

Added subscriber: @ronsn

ronsn commented

2020-06-21 23:03:32 +02:00

@EAW Okay, it's a design change and that's fine. But why didn't they take into account to change it for .blend files too? You said developer want to know in which version a file was saved. Yes and that is why it is important that bpy.app.version and bpy.data.version should be comparable.

The documentation says:

bpy.data.version reflects the version of Blender in which the file was saved
bpy.app.version reflects the version of Blender instance which is currently running

So it doesn't matter if they change the versioning system, but then either they apply the change to both, or they should document, that bpy.data.version is no longer the version of Blender in which the file was saved! They didn't do either and therefore this is a valid bug report.

@EAW Okay, it's a design change and that's fine. But **why** didn't they take into account to change it for .blend files too? You said developer want to know in which version a file was saved. Yes and that is why it is important that `bpy.app.version` and `bpy.data.version` should be comparable. The documentation says: - `bpy.data.version` reflects the version of Blender in which the file was saved - `bpy.app.version` reflects the version of Blender instance which is currently running So it doesn't matter if they change the versioning system, but then either they apply the change to both, or they should document, that `bpy.data.version` is no longer the version of Blender in which the file was saved! They didn't do either and therefore this is a valid bug report.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

bpy.app.version and bpy.data.version are reporting different version numbers from Python interactive console #77489