gresm

Something a bit similar happens when filling a surface and rotating it. This code: ```py import pygame as pg from time import sleep pg.init() surface = pg.Surface((100, 100)) surface.fill((255, 255,...

@oddbookworm I also believe that this is intentional, but doesn't seem to be well-documented behaviour, or at least I wasn't able to find anything about it in the docs.

> Apart from the merge issues this looks good to me @MyreMylar Merge issues have been now fixed.

Linking this pull request to the issue.

Fixes #2997

So it wasn't even intended to work this way?

Indeed it would break, but this is not the valid way of checking python types (by peps), so should we really worry about exact this corner case?

There is an issue with this enhancement: Vectors in pygame are mutable, but tuples are not. Making a mutable object of a subclass that inherit from immutable may cause weird...

I propose instead, adding immutable version of Vectors, for that exact situation, I imagine holding a reference to a vector, to update value of eg: Rect may be an useful...

Operationg system: ``` $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 21.10 Release: 21.10 Codename: impish ``` Java version: ``` $ java --version openjdk 11.0.15...