We do not handle user support on this tracker, only bug reports. User forums like blenderartists.org or blender.stackexchange.com should be used for that matter.

This will be enabled in 2.8, see rBaa5a96430ea0741fac39b87fe17fb0faddadd3cf

Implemented in rBaa5a96430ea0

If at least vector * vector doesn't do a dot product, I'm happy ^^
I wasn't aware of the @ possibility and I am also not familiar with numpy, but it definitely sounds like a good idea to follow a similar convention :)

As per review comments on D3587, I've also implemented:

• matrix @= matrix
• matrix *= matrix/float
• quat @= quat
• quat *= quat/float

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

@Inês Almeida (brita_) / @Andrew Hale (trumanblending), what about following numpy conventions for cases which are disputable?

I suggest to leave this one out, since Blender uses column vector convention. Having it, could confuse people as to the order of multiplication of the matrices.
Vector @ Matrix (vector interpreted as row vector)

Not sure why that’s assigned to me… Guess @Campbell Barton (campbellbarton) will want to check on that?

Fixed rBfe8d8aa27e26f1f8e4d5e1e3fcb6fc6288ebf226

Your blender installation is corrupted somehow, please:

• Give us your exact Blender, OS and GPU (including drivers) versions, as requested in the template!
• Ensure both your OS and drivers are fully up-to-date (and use official GPU drivers, not those provided by windows or tablet/laptop maker or open source ones in linux distributions).
• For Windows 7, at least service pack 1 is mandatory, please ensure it is installed on your machine.
• Try to disable any running antivirus.
• Ensure you have no python executable available in your %path% envvar.
• 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).

It was actually a Cycles issue due to rBf8b9f4e9bbc1: Cycles: Resumable render implementation for Cycles.

Confirmed.

@Brecht Van Lommel (brecht), @Arto Kitula (akitula) , mind checking that one? Thanks.

Can't redo this in Linux, looks like an OSX only issue?

Will check yes.

Checking code of said isect_ray_aabb_v3_simple makes it obvious it does not care whether direction is normalized or not, for its 'match or not match' main result.

Fwiw, on 2.8 it seems to work OK, so will consider that issue as fixed. Thanks for the report!

@Brecht Van Lommel (brecht) maybe you want to check on that one? Thanks.

YES PLEASE FOR A NEW CALLBACK! I'll add some further context to my desire to upvote this proposal. I am currently in the category of having to use 'loop kicking' (interesting term for it, but its what we have to do). We need to be able to run an event loop to capture msgs to our distributed rendering platform for blender. Msgs come back to blender from other nodes, currently we've had to use a modal operator with a timer to implement async operations. I got excited about asyncio a while back, but realised that it needed to have the same modal operator to work. If there was an event that could be subscribed to that would avoid the need to have a modal operator running this would be excellent. Modal operators when used for look kicking have some pretty undesirable drawbacks;

Another argument for Python 3.7 is the expanded capabilities of the asyncio library.
"The asyncio module has received many new features, usability and performance improvements. Notable changes include:"
https://docs.python.org/3/whatsnew/3.7.html#whatsnew37-asyncio

@Campbell Barton (campbellbarton) should know that area of code well. ;)

I really think this should be looked at again.

Thank you @Bastien Montagne (mont29) . I did discover a workaround which was to wrap the script in a function that is appended to the app handlers. Consider the following script:

Took me some time to understand what is happening here… thing is, we do some backup/sanitizing of context before executing py scripts, and among other things, arg_py_context_backup calls CTX_wm_window_set, which sets again context's Scene from active windows' screen scene…