There was also T48096 and T54097, but to be honest: I am unaware of any 'final' decision on this...
Will also talk to @Campbell Barton (campbellbarton) again...

Please also leave me out of this and future conversation. Thanks.

Sounds like your mess. Please leave me out of this and future conversation. Thanks

I imported all the release notes I think we agreed that we would not migrate addon docs as for 2.8 we wont have them on the wiki anyway.

Sounds like the old pages need to be migrated, and possibly some redirects added, exactly like you just said above. IIRC, we've discussed this several times already? I assume you've finished migrating the old wiki? I could have sworn that's why I gave you the import/export access a month or two ago.

@Dan McGrath (dmcgrath) Can you insight some wisdom here?

Thank for the subscription here and my apologize to not have been able to find this bug was already reported there before posting my version.

Eeek, yes indeed, actually it returns evaluated version of the object (COW, you know…), not the 'real' data from bpy.data… will fix.

Checked again with factory startup file.

No bug here, error message is self-explanatory really. Just how new 2.8 system works.

Please create a differential, it’s correct way to submit patches now. :)

This is a known issue ever since we moved to the new wiki, and not really anything we can do except just saying that "It will be fixed in 2.8".
The documentation is still hosted temporally on https://en.blender.org/index.php/Extensions:2.6/Py/Scripts but this will be removed once we migrate the needed pages over to the new wiki.

There are gazillions of ways to make Blender crash with bad py code… ideally yes, that should be checked in the poll callback of the operators, but that’s not a bug.

I was working with him on this script, we did end up getting it to work, and yes, the context was the problem... but regardless, shouldn't blender give an error rather than just crashing? Seems like it is still a bug.

OK finally managed to reproduce (that operator only works when VSE editor is in only-preview mode).

Strange. It crashes here on 2.8 too.

Cannot reproduce any crash here with this code (once tabulation is fixed…). Please at the very least give us error message!

again…

@Amir (Warrior) nothing prevents you from using system python instead of 'own' blender one, just ensuer you build with system python, disable the WITH_PYTHON_INSTALL build options, and blender will use system python, and you can use any module installed there. That would be by far the simplest solution (especially on linux, where valid system python should nearly always be available).

@Brecht Van Lommel (brecht) I think I fixed it actually but this is not a permanent solution and I'm not work if Armory is going to work properly this way.

@Brecht Van Lommel (brecht) No it shows me the following error although I ran the code above to install it.

I'm not sure I understand, doesn't bpy.ops.wm.addon_enable(module='armory') work, you just have to call it every time?

@Brecht Van Lommel (brecht) I think it's totally understandable to assume that people who compile Blender as Python module would ONLY need to use the "factory setting" functionalities, but it's not a good idea not to provide an option for others to be able to install addons :(

@Bastien Montagne (mont29) I don't have an issue running Blender with the -b flag but the reason that I'm compiling Blender as Python module is that I have many other packages that I'm using in my project and things are integrated. I do import pytorch, import cv2 etc and it's not possible to disentangle things. On the other hand, I don't think it is possible to compile a heavy code base like PyTorch and add its module into the internal Python that Blender comes with.

@Amir (Warrior) no, blender-as-module is a library, not an application. Blender with no GUI is… Blender with no GUI (run from commandline with -b option, you can even build it with WITH_HEADLESS option to actually have no available GUI at all).

@Campbell Barton (campbellbarton) @Brecht Van Lommel (brecht) But it doesn't make sense not to be able to install addons if you're using the Python module. The Python module should be Blender with no GUI in my opinion and there shouldn't be any difference. Would you agree with that?
But still, is there a way to manually load a userpref.blend file with the Python module? How can one install addons when using the Python module?

The Python module indeed always starts with "factory settings" by design. This is what you would normally expect from a programming API I think.

@Campbell Barton (campbellbarton) will know more here, but am pretty sure blender-as-py-module does not handle at all user preferences and such? That would not make much sense at least, imho…

I have attached the blend file. When I open that file, select the console which already has the command typed in, and press ctrl + space, blender crashes.

Please attach the blend file that crashes.

After downloading the latest version of Blender (Hash 265ec400ab1) and running in factory mode, the error no longer occured. However with the default settings that I had set up, the error did occur. I have attached the printed error as a text file in case it is still of interest.

@Campbell Barton (campbellbarton) / @Alexander Gavrilov (angavrilov)
Given that quaternions are somewhat more specialised than the other types, I've removed any changes to element-wise ops for them in D3642 (i.e. they behave as before).

Cannot reproduce either. Please:

• Try to re-download and re-install Blender.
• Try the latest build from our buildbot.
• Try to start Blender in factory settings (--factory-startup commandline option) (this will ensure whether this is a userpref or addon issue or not).
• Launch Blender from the command line with -d option and attach as text file here any error printed out in the console (do not paste it directly in comment).