Blender 3.0 (Python API deprecation, updates) #85675

New Issue

Campbell Barton · 2021-02-16T02:39:18+01:00

Campbell Barton commented

2021-02-16 02:39:18 +01:00

This task is intended to track breaking changes to be made for Blender 3.0

- Remove deform argument from BMesh.from_object (already listed as deprecated). ead084b6e1
- Remove active_base (bpy.context.active_base) 44db4e50b2

All other access to the `Base` structure was removed, it seems this was left in by accident. None of the scripts or add-ons distributed with Blender use this.

- Remove IDPropertyGroup.iteritems

Rename the current `iteritems` method to `items`. {rB265d97556aa0f0f2a0e4dd7584e3b8573bbddd54}

This was a hang-over from Python 2.x which used both methods for dictionary types, now defaulting to the iterable version in Python 3.0.

- Remove deprecated wiki_url handling from add-on's bl_info in favor of doc_url. aaa07a3a8f
- Use keyword only arguments in the C/API, to avoid breaking scripts when changing arguments. (f29a738e23)
#84638 (Radius and diameter mixup for primitive spheres)
Remove Context.region_data, Use Context.region.data instead (see: 9cfb320208)

Open Topics:

blender/blender-addons#80730 (BGL deprecation) (the GPU module needs to be further developed before a decision is made).

This task is intended to track breaking changes to be made for Blender 3.0 - - [x] Remove `deform` argument from `BMesh.from_object` (already listed as deprecated). ead084b6e1 - - [x] Remove `active_base` (`bpy.context.active_base`) 44db4e50b2 ``` All other access to the `Base` structure was removed, it seems this was left in by accident. None of the scripts or add-ons distributed with Blender use this. ``` - - [x] Remove `IDPropertyGroup.iteritems` ``` Rename the current `iteritems` method to `items`. {rB265d97556aa0f0f2a0e4dd7584e3b8573bbddd54} ``` ``` This was a hang-over from Python 2.x which used both methods for dictionary types, now defaulting to the iterable version in Python 3.0. ``` - - [x] Remove deprecated `wiki_url` handling from add-on's `bl_info` in favor of `doc_url`. aaa07a3a8f - - [x] Use keyword only arguments in the C/API, to avoid breaking scripts when changing arguments. (f29a738e23) - #84638 (Radius and diameter mixup for primitive spheres) - Remove `Context.region_data`, Use `Context.region.data` instead (see: 9cfb320208) ---- ### Open Topics: - blender/blender-addons#80730 (BGL deprecation) (the GPU module needs to be further developed before a decision is made).

Campbell Barton self-assigned this 2021-02-16 02:39:18 +01:00

Campbell Barton commented

2021-02-16 02:39:18 +01:00

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

Campbell Barton commented

2021-02-16 02:39:18 +01:00

Added subscriber: @ideasman42

Campbell Barton commented

2021-02-16 02:40:44 +01:00

Added subscribers: @mont29, @dr.sybren

Bastien Montagne commented

2021-02-16 09:33:30 +01:00

I would definitively also include the keyword-only change in 3.0...

blender-admin commented

2021-02-17 16:45:52 +01:00

This issue was referenced by blender/blender-addons@f01d08b7c5

This issue was referenced by blender/blender-addons@f01d08b7c5f7873e0ce8a77b84788e2f6b1ad716

Mindinsomnia commented

2021-03-10 04:04:35 +01:00

Added subscriber: @Grady

Mindinsomnia commented

2021-03-10 04:04:35 +01:00

Suggestion for possible 3.0 change:

BMesh operators [bmesh.ops.duplicate ]] and [ https:*docs.blender.org/api/current/bmesh.ops.html#bmesh.ops.split | bmesh.ops.split both have an unimplemented parameter, 'dest', which is meant to provide the option to duplicate or split a section of mesh into another destination bmesh.

Either the destination mesh argument should be implemented (which would be my preferred outcome) or removed since right now it provides no benefit at best and serves to create confusion at worst (especially since the API docs don't mention they aren't implemented, I only discovered it myself recently while writing an addon).

Suggestion for possible 3.0 change: BMesh operators [bmesh.ops.duplicate ]] and [[ https:*docs.blender.org/api/current/bmesh.ops.html#bmesh.ops.split | bmesh.ops.split ](https:*docs.blender.org/api/current/bmesh.ops.html#bmesh.ops.duplicate) both have an unimplemented parameter, **'dest'**, which is meant to provide the option to duplicate or split a section of mesh into another destination bmesh. Either the destination mesh argument should be implemented (which would be my preferred outcome) or removed since right now it provides no benefit at best and serves to create confusion at worst *(especially since the API docs don't mention they aren't implemented, I only discovered it myself recently while writing an addon).*

hujin commented

2021-03-24 03:30:27 +01:00

Added subscriber: @2046411367

Eitan Traurig commented

2021-04-16 16:47:22 +02:00

Added subscriber: @EitanSomething

Eitan Traurig commented

2021-04-16 16:47:22 +02:00

Suggestion for possible 3.0 change: I am willing to implement it

Move bpy.types.MovieClip.use_proxy_custom_directory to bpy.types.MovieClipProxy.use_proxy_custom_directory.

Use_proxy_custom_directory is currently under bpy.types.MovieClip for MovieClipbut for ImageSequenceand MovieSequenceit is under bpy.types.SequenceProxy. This inconsistency makes it difficult to read/write code, which checks sequences in the video sequence editor to see if they are using a custom directory. (example of unnecessarily complex code currently needed D6139)

Suggestion for possible 3.0 change: **I am willing to implement it** Move `bpy.types.MovieClip.use_proxy_custom_directory` to `bpy.types.MovieClipProxy.use_proxy_custom_directory`. Use_proxy_custom_directory is currently under `bpy.types.MovieClip` for **MovieClip**but for **ImageSequence**and **MovieSequence**it is under `bpy.types.SequenceProxy`. This inconsistency makes it difficult to read/write code, which checks sequences in the video sequence editor to see if they are using a custom directory. (example of unnecessarily complex code currently needed [D6139](https://archive.blender.org/developer/D6139))

Campbell Barton commented

2021-05-11 03:32:57 +02:00

Added subscriber: @Sergey