To me this seems non-standard enough to not even have it as a preference, unless it's common in other REPL apps.

Hi, I'm aware of the possibility of adding emacs/bash/readline key shortcuts but would prefer to avoid this for the default keymap.

Sounds reasonable, will check with others though [and commit if agreed upon]

We discussed solutions to this type of problem, @Sergey Sharybin (sergey) will probably be the one to implement it.

Wow :D my first python fix! Thank you a lot, you are awesome!

also note there was very similar T61264

I just tested today build 4th of april, and this file no longer crashes. It seems bug was fixed.

I think that the root cause it probably the same as in T60766

@Jose Conseco (joseconseco), in the future, please use the bug reporting form:
https://developer.blender.org/maniphest/task/edit/form/1/

Backtrace:

Thread 1 "blender" received signal SIGSEGV, Segmentation fault.
0x00007fffeba89c17 in ?? () from /lib64/libc.so.6
(gdb) bt
#0  0x00007fffeba89c17 in ?? () from /lib64/libc.so.6
#1  0x00005555592b8755 in copy_m4_m4 (m1=0x7fffbc6a5a2c, m2=0x40) at /home/zed/prog/blender/source/blender/blenlib/intern/math_matrix.c:88
#2  0x0000555558015a95 in setTransformViewMatrices (t=0x7fffbc6a5708) at /home/zed/prog/blender/source/blender/editors/transform/transform.c:235
#3  0x00005555580762e9 in initTransInfo (C=0x7fffdc058188, t=0x7fffbc6a5708, op=0x7fffbc5dfec8, event=0x0)
    at /home/zed/prog/blender/source/blender/editors/transform/transform_generics.c:1681
#4  0x000055555801b1ac in initTransform (C=0x7fffdc058188, t=0x7fffbc6a5708, op=0x7fffbc5dfec8, event=0x0, mode=1)
    at /home/zed/prog/blender/source/blender/editors/transform/transform.c:2340
#5  0x0000555558086e01 in transformops_data (C=0x7fffdc058188, op=0x7fffbc5dfec8, event=0x0)
    at /home/zed/prog/blender/source/blender/editors/transform/transform_ops.c:370
#6  0x0000555558087092 in transform_exec (C=0x7fffdc058188, op=0x7fffbc5dfec8) at /home/zed/prog/blender/source/blender/editors/transform/transform_ops.c:463
#7  0x0000555557e63e48 in wm_operator_invoke (C=0x7fffdc058188, ot=0x7fffd6dfab88, event=0x0, properties=0x7fffffffcd90, reports=0x7fffb97fabb8,
    poll_only=false, use_last_properties=true) at /home/zed/prog/blender/source/blender/windowmanager/intern/wm_event_system.c:1353
#8  0x0000555557e6464b in wm_operator_call_internal (C=0x7fffdc058188, ot=0x7fffd6dfab88, properties=0x7fffffffcd90, reports=0x7fffb97fabb8, context=6,
    poll_only=false, event=0x0) at /home/zed/prog/blender/source/blender/windowmanager/intern/wm_event_system.c:1586
#9  0x0000555557e64899 in WM_operator_call_py (C=0x7fffdc058188, ot=0x7fffd6dfab88, context=6, properties=0x7fffffffcd90, reports=0x7fffb97fabb8,
    is_undo=false) at /home/zed/prog/blender/source/blender/windowmanager/intern/wm_event_system.c:1664
#10 0x00005555585af25d in pyop_call (UNUSED_self=<module at remote 0x7fffd7068688>, args=Python Exception <class 'gdb.error'> No type named PyUnicodeObject.:
)

Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given.
(@Michael Demetriou (qwazix) : just reopen if you've checked and issues persist)

This was really fast. Thank you very much, Campbell!

Solved in rB22dc248f14be: Fix T56610: crash saving images with python API..

It's nice to hear you say that something is easy, related to node trees haha

@Jacques Lucke (JacquesLucke) I think this is fairly easy to add (just call the function adding sockets to group's nodetree instead in RNA code), trying it currently…

I'm pretty sure that this is not supposed to work.
I actually don't know the API to add sockets to groups, but I guess it has to be done "from the inside".

Confirmed, bpy.context.scene.node_tree.nodes['Group'].node_tree.inputs.new('NodeSocketColor','stuff') is working as expected (the direct access from Group node's inputs should be a shortcut to that one I think, or not allow this operation at all, checking code…)

Right, modal keymap handler isn't guaranteed to get all events - other modal operators and popups can swallow the events before they reach this modal operator.

I will have to check, but this might take a while.

Still should not crash I guess..

Is this still happening in blender 2.8?

I can confirm that there is something weird going on. If I open blender and paste in that script and run it and then use the Props Dialog, blender soft hangs for me as soon as I press the OK button.

Solved by Blender developers themselves in https://developer.blender.org/rBcae89a6889e0fc03130a56b6bf84e257eaff0fec

More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.

More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.

I just noticed when I add 'USE_EVAL_DATA' to operator bl_options
bl_options = {"REGISTER", "UNDO","USE_EVAL_DATA"}
Then crash won't happen. I'm not sure if this bug should be marked as fixed then.

This bug has been open a month without being addressed, so I'm going to use Phillip's suggested Python workaround. A fix before 2.80 ships would be appreciated!

The commit that caused this was reverted, another solution without this problem should be implemented.

CTX_wm_region(C) returns NULL in uiTemplateList(..) directly after the file selector is closed.
When I skip the function in this case, everything goes back to normal on the next redraw.

of course. Just wasn't sure what's easier to debug. I tried to strip it down as best as I could:

I can reproduce it. Can you try to remove everything from that script that is not necessary to reproduce the bug? That would make debugging a bit easier.

By the way, some functions (rna_Object_select_get, rna_Object_visible_get, ...) are missing the view_layer parameter and always get the selected/visible/etc. state from the current context's view layer, while other functions (rna_Object_holdout_get, indirect_only_get) require to specify the view layer explicitly. Is this an oversight or an intentional design?

In T61923#627800, @Jon Seigel (jseigelis) wrote:

Oh, my bad, I didn't mean to step on your toes.

Naah.

Oh, my bad, I didn't mean to step on your toes.

You have to loop over all elements, this won't be efficient.

Maybe you will have advice to get the current selection? I am very worried about performance. Since the addon will work all the time in the background.

I also rewrote this operator in patch D4290: VSE new python operators

This isn't a bug, selection history only for for picking individual elements.

I would be happy to give an example of how to transfer the coordinates of a real object, rather than enter them manually.
https://docs.blender.org/api/blender2.8/gpu.html#wireframe-cube-using-index-buffer

Thank you for providing an fix for that issue.

I have updated my Blender to yesterday's version and am unfortunately still having the same crashes.
I also updated my sample code in the first post, seems I deleted too much code when I was simplifying it. I am very sorry for that.
It should work (or rather crash) as intended now. I even added a small panel for convenience's sake.

I cannot reproduce this in the current build. Please check if the issue still exists.
If yes, then please start Blender from the terminal and post the output here.

Ok. Thanks for Your help, and sorry for posting it here.

thanx @Bastien Montagne (mont29) for clearing that up! (sorry for my uneducated fiddeling here...)

Thanks again!

First of all, this is not a bug report at all, and should not be handled here. We have a site for that kind of question: https://devtalk.blender.org/

I can only repeat myself: I am on shaky ground here, if the above file doesnt work for you, I am probably out of ideas...

Sorry, Your blend file was not empty, my mistake. But the error still occurs.

Not sure if this is the recommended way, but picking a region type for your spacetype that doesnt draw panels automatically seems fine, I guess...
So for space TEXT_EDITOR, you could use bl_region_type = 'HEADER', bl_region_type = 'WINDOW'?

This .blend file You attached is (as far as I know) default init blend file, so I can't check what You have changed. Please attach the changed .py file.
I followed Your directions:

• I removed enumerate (It was there for testing purposes anyway), but this did not solve the problem.
• I assume that Your step 2 was passing 'deepcopy(branch['sub_items'])' instead of ''branch['sub_items'] into the recursive function. It did not solve the problem for me (did it for You?). Please remember that (like I wrote in the comments of my py file) calling operator again does not replicate the error: "I have to restart blender to repeat the error". And after that changes error is still there. Also, the problem from Your link is little different from mine, because my problem is with 'current_item' variable (not with ''branch['sub_items']"). I am not passing 'current_item' to the recursive call, and as far as I know my current_tems variables from every scope point to a different object, coz I create it in the scope, not passing it as a parameter.

Regards.

Thanks! layout.popover() seems like exactly what I need.

Can confirm the crash (when accessing/printing the current_item after the recursive call)

?

Oki, closing then

I don't think it's a bug. I think this is just a limitation of the menu system. For more custom layouts, use a popover.

Menus are a bit limited in regards to layout.
I dont have an exact list of these limitations (I just remeber I had an issue in D4215 as well).

I think this isn't worth worrying about, we could use from __future__ import print_function all over for our utilities, but in practice we never had people adding back old style print statements.

See Prevent compatibility regressions The future import makes legacy print statements syntax errors even in Python 2 which prevents Python 2 developers from making changes which break Python 3 compatibility.

Committed rB7262ac6202eb9258293473f35a24f375f9d6f635, no need for __future__