Adam Griffiths

Can you see if this is still an issue with 0.10.3 which has some fixes from https://github.com/adamlwgriffiths/Pyrr/pull/88

The idea is to mimic the numpy behaviour as much as possible. If you pass in ints to a np.narray, you'll get an array of ints. Same thing here. The...

There are valid uses for integer matrices (https://en.wikipedia.org/wiki/Integer_matrix). I do not use these but I am not here to dictate mathematics. The idea is to mimic numpy's behaviour. Similar interface...

As long as nothing is removed by adding this, then I'm all for removing pit-falls. It seems there is an np function that could be used to provide some hints...

No, stick to standard float definition, which is float64. The code snippet above should be pretty much all that is needed.

The relevant argument for the function in question. Ie, depends on the context =P. For `create_from_axis_rotation` it would be `axis`, for `create_from_quaternion`, it would be `quat`, etc. I may be...

The current geometric testing API is limited and needs to be changed to return a structure of points, segments, lines, etc Something like: ``` {'points': [], 'segments': [], 'lines': [],...

Looks like the object interface ```m1 * m2``` [expands to](https://github.com/adamlwgriffiths/Pyrr/blob/master/pyrr/objects/matrix33.py#L178) ```multiply(m2, m1)``` which then [expands to](https://github.com/adamlwgriffiths/Pyrr/blob/master/pyrr/matrix33.py#L322) ```np.dot(m2, m1)``` I'm not sure what the reasoning for it was, it's obviously inappropriate.

PRs are welcome

Some changes were applied in #108, can you test if the latest changes fix this for you?