[Python-modules-team] Bug#798010: Info received (Bug#798010 closed by Julian Taylor <jtaylor.deb...@googlemail.com> (Re: Bug#798010: Bug#798010: ipython3: malicious dynamic python3 interpreter lookup

2015-09-18 Thread Tobias Megies
odule named 'IPython' This looks pretty odd, does it not? regards, Tobias Megies On 09/18/2015 12:00 PM, Debian Bug Tracking System wrote: > Thank you for the additional information you have supplied regarding > this Bug report. > > This is an automatically generated reply to let

[Python-modules-team] Bug#798010: closed by Julian Taylor <jtaylor.deb...@googlemail.com> (Re: Bug#798010: Bug#798010: ipython3: malicious dynamic python3 interpreter lookup via "/usr/bin/env python3"

2015-09-18 Thread Tobias Megies
a change. Thus I am closing the issue. I can really not follow your reasoning to ignore this bug.. at all. Why deviate from the Python Policy? regards, Tobias Megies On 09/04/2015 05:06 PM, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug re

[Python-modules-team] Bug#798010: ipython3: malicious dynamic python3 interpreter lookup via "/usr/bin/env python3" in main executable

2015-09-04 Thread Tobias Megies
y checking and makes the package vulnerable to incomplete local installations of python. === quote end best regards, Tobias Megies -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_6

[Python-modules-team] Bug#725047: python-matplotlib: missing recommends/suggests in debian/control

2013-09-30 Thread Tobias Megies
Package: python-matplotlib Version: 1.1.1~rc2-1 Severity: serious Justification: Policy 5.6.10; 7.2 Dear Maintainer, several packages that are used inside the matplotlib code seem to be missing from Depends/Recommends/Suggests in debian/control. One example is the test suite. It can not be run

[Python-modules-team] Bug#719065: fixed upstream; part of upcoming bugfix release 1.3.1 in upstream

2013-09-29 Thread Tobias Megies
This bug has been fixed upstream, see https://github.com/matplotlib/matplotlib/pull/2307. The fix will be part of the upcoming bugfix/minor release 1.3.1 of matplotlib. I assume unstable will be updated to 1.3.1 after it is released? After/if it is updated this bug can be closed. best, Tobias

[Python-modules-team] Bug#719065: (no subject)

2013-08-24 Thread Tobias Megies
I think this is the same problem as in issue #2320 at the matplotlib github page: https://github.com/matplotlib/matplotlib/issues/2320 ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org