[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#585322: marked as done (python-pysnmp-se: Python string exceptions no more allowed in Python 2.6)

Your message dated Mon, 14 Feb 2011 12:26:09 +0000
with message-id <[🔎] E1PoxVJ-0002yH-6n@franck.debian.org>
and subject line Bug#613286: Removed package(s) from unstable
has caused the Debian Bug report #585322,
regarding python-pysnmp-se: Python string exceptions no more allowed in Python 2.6
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
585322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585322
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: python-pysnmp-se
Version: 3.5.2-5
Severity: minor
User: debian-python@lists.debian.org
Usertags: python2.6

Hello,
One of the changes brought by Python 2.6 is the removal of string
exceptions, so they won't work in Python 2.6 (just a side note: they
were also buggy before, since they were not guaranteed to work
reliable even in <2.6); as an example:

$ python2.5 -c "raise 'eggs'"
-c:1: DeprecationWarning: raising a string exception is deprecated
Traceback (most recent call last):
  File "<string>", line 1, in <module>
eggs

$ python2.6 -c "raise 'eggs'"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
TypeError: exceptions must be old-style classes or derived from BaseException, not str

Since 2.6 is the planned default version for the upcoming new Debian
stable release, there are chances your package may be affected by this
change.

We are not sure your package is impacted, since the exception raise
can be in a dead or very rare branch of the code, and so simply never
being executed. We would like to leverage your package maintainer
status and the relationship with upstream authors to inspect more
deeply the issue and act accordingly (that includes: making this bug
release critical, closing it as irrelevant, tagging it 'wontfix', or
whatever is appropriate).

Jakub Wilk made the discovery of the problem and kindly prepared a
list [1] of all identified packages (downloaded on 2010-06-09) along
with files & lines that triggered the pattern search.

[1] http://people.debian.org/~morph/strexp/string-exceptions.lintian

This mass-bug filing was announced at 2010-06-06 on [2] (see the
thread and the references there).

[2] http://lists.debian.org/debian-devel/2010/06/msg00097.html

We do not consider the whole situation a stopper for the Python
transition to 2.6, except (of course) for those single bugs where
severity will be increased.

Thanks in advance for your attention,
Sandro on behalf of debian-python

--- End Message ---
--- Begin Message --- 
Version: 3.5.2-5+rm

Dear submitter,

as the package pysnmp-se has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see http://bugs.debian.org/613286

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@debian.org.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)

--- End Message ---
Reply to: