[Python-modules-team] Bug#750895: python3-tempita: doesn't work with python 3.3

Hi, 1. I observed exactly the same occurs also with stretch and Python 3.6.0. I believe any future versions will suffer from the same error because it stems from the different ways how encoding and bytearray are treated in Python 2.x and Python 3.x. 2. This issue is already fixed in the

[Python-modules-team] Bug#854716: Bug#854716: python3-django-cors-headers: Does not work with Django 1.10

Michael Fladischer writes: > Updating to 1.2.0 would solve this but the freeze is already in place, so it's > either backporting the fix from upstream[0] or asking fo an exeption from > release team. Unblock request sent for backport: #854833 -- Brian May

[Python-modules-team] Bug#854716: marked as done (python3-django-cors-headers: Does not work with Django 1.10)

Your message dated Fri, 10 Feb 2017 22:18:35 + with message-id and subject line Bug#854716: fixed in django-cors-headers 1.1.0-2 has caused the Debian Bug report #854716, regarding python3-django-cors-headers: Does not work with Django 1.10 to be marked as

[Python-modules-team] django-cors-headers_1.1.0-2_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 11 Feb 2017 08:34:43 +1100 Source: django-cors-headers Binary: python-django-cors-headers python3-django-cors-headers Architecture: source all Version: 1.1.0-2 Distribution: unstable Urgency: medium Maintainer:

[Python-modules-team] Processing of django-cors-headers_1.1.0-2_amd64.changes

django-cors-headers_1.1.0-2_amd64.changes uploaded successfully to localhost along with the files: django-cors-headers_1.1.0-2.dsc django-cors-headers_1.1.0.orig.tar.gz django-cors-headers_1.1.0-2.debian.tar.xz django-cors-headers_1.1.0-2_amd64.buildinfo

[Python-modules-team] m2ext 0.1-1.1 MIGRATED to testing

FYI: The status of the m2ext source package in Debian's testing distribution has changed. Previous version: 0.1-1 Current version: 0.1-1.1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive

[Python-modules-team] Bug#854390: marked as done (python-bottle-cork: insecure default hashing algorithm)

Your message dated Fri, 10 Feb 2017 09:49:19 + with message-id and subject line Bug#854390: fixed in python-bottle-cork 0.12.0-2 has caused the Debian Bug report #854390, regarding python-bottle-cork: insecure default hashing algorithm to be marked as

[Python-modules-team] python-bottle-cork_0.12.0-2_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 10 Feb 2017 10:04:27 +0100 Source: python-bottle-cork Binary: python-bottle-cork python3-bottle-cork Architecture: source Version: 0.12.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules

[Python-modules-team] Processing of python-bottle-cork_0.12.0-2_amd64.changes

python-bottle-cork_0.12.0-2_amd64.changes uploaded successfully to localhost along with the files: python-bottle-cork_0.12.0-2.dsc python-bottle-cork_0.12.0-2.debian.tar.xz python-bottle-cork_0.12.0-2_amd64.buildinfo Greetings, Your Debian queue daemon (running on host

[Python-modules-team] Bug#854716: Bug#854716: python3-django-cors-headers: Does not work with Django 1.10

Michael Fladischer writes: > the version of django-cors-headers currently in testing/unstable does not work > with Django 1.10 because of changes to the middleware system. Upstream has an > issue on this: It looks like it is a bit more complicated then "does not work". If you