Package: renpy Version: 8.0.3+dfsg-1 Severity: serious
pitfall n°1: there's no version 8.2.0: it's a daily snapshot, we need to wait for a proper release pitfall n°2: removing python3-future from RenPy seems not so complicated but that _may_ or not break games if they depends on renpy/compat/__init__.py I don't know how/where to find such game. It would be stubbed somehow. $ renpy/compat/__init__.py """ This module is defined to allow us to program in Python 2 with a high degree of compatibility with Python 3, and vice versa. It's intended to be invoked with the following preamble:: from __future__ import division, absolute_import, with_statement, print_function, unicode_literals from renpy.compat import * Right now, it does the following things: * Sets up aliases for Python 3 module moves, allowing the Python 3 names to be used in Python 2. * Defines PY2 in the current context, to make Python 2 conditional. * Aliases pickle to cPickle on Python 3, to support Python 2 code choosing between the implementations, where the choice is meaningful * Replaces open with a function that mimics the Python 3 behavior, of opening files in a unicode-friendly mode by default. * Redefines the text types, so that str is always the unicode type, and basestring is the list of string types available on the system. * Exposes bchr, bord, and tobytes from future.utils. * Changes the meaning of the .items(), .keys(), and .values() methods of dict to return views, rather than lists. (This is a fairly major change, and so is only available when with_statement and division are both imported. * Aliases xrange to range on Python 2. * Changes the behavior of TextIOWrapper.write so that bytes strings are promoted to unicode strings before being written. """