>> So I'd argue that ‘python3-mock’ and the like do have a place in Debian: >> they make it easier to follow the recommended strategy of having a code >> base run unchanged on Python2 and Python 3. As it turns out, it looks like upstream enum34 is going to rename the import to 'enum34' so it won't conflict with built-in enum. It's still not Python 3.5 compatible yet (the test suite fails) but maybe that makes removing it a moot point. Cheers, -Barry