Inconsistent python api and documentation in mathutils. #47337
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#47337
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Blender Version
Broken: blender/blender@a6ca8a1b73
Short description of error
While the api docs show mathutils.bvhtree.BVHTree.find_nearest() this does not exist in the python api.
Exact steps for others to reproduce the error
In blender's pythjon console we get the following -
I expect that the method name
find_nearest
would be correct as it is the most used within the code and better describes the function. This mismatch stems from the api definition inmathutils_bvhtree.c
with a fix being -There is a possibility that
BVHTree.find()
is already in wide use and adjusting the documentation to match the use ofBVHTree.find()
will be less disruptive.Changed status to: 'Open'
Added subscriber: @sambler
This issue was referenced by blender/blender@c7608ef359
Changed status from 'Open' to: 'Resolved'