Standalone PySide2 wheels

The Qt Company has yet to release official, standalone and pip-installable PySide2 wheels. However, since they made it possible to build standalone wheels successfully, I’m now building such unofficial, standalone wheels here using free CI services (thanks Travis and AppVeyor!):

Update 2018-03-09: The Qt Company now offers official and standalone wheels, read more here! Update 2018-07-17: PySide2 can now be installed from pip install PySide2!


Dates and databases with Python

It’s a bit tricky to deal with dates, timezones and daylight savings when you need to store dates in e.g. a database for later reading.

To me, it’s a bit perplexing that all tools required to deal with this doesn’t come with the Python standard library (meaning; batteries are not included). Instead we need to use three different modules: datetime, pytz and tzlocal where the two latter ones are not part of the standard library and must be installed separately via e.g. pip.

Here follows some personal notes on how to store and read back dates with reliability and control of the timezones and daylight savings.


Querying the FPS preference in Maya

This tickles the funny bone.

>>> import maya.mel as mel
>>> fps = mel.eval('float $fps = `currentTimeUnitToFPS`')
>>> print(fps)

Maya 2018 file size bug

A very annoying bug came to light in mid-October which makes Maya 2018 binary scene files (*.mb) unreadable if they are larger than ~2 GB in size.

To be exact, the bug is hit when the file size is larger than 2147483647 bytes, the maximum positive value for a 32-bit signed binary integer.


Contributing to PySide2

This is reminder-to-self about how to get set up and contribute to PySide2 using Gerrit. It could also be a fun read “on the bus” before actually setting this up yourself, to get an overview on what’s required to get up and running with Gerrit.

Disclaimer: I discourage you to blindly follow these highly personal notes without reading through the official docs when you actually get set up yourself. Anything can be changed in the official docs at any time, which isn’t reflected here. The point of this post is just to make a note-to-self and offer a “bigger picture” before actually digging in.