[FFe] python-markdown 2.6

Bug #1423851 reported by Dmitry Shachnev
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-markdown (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I would like to see python-markdown 2.6 (which was released today) in vivid. Despite having some new features and changes (see changelog [1]), it fixes some important bugs like [2] and [3].

[1] http://pythonhosted.org/Markdown/release-2.6.html
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776591
[3] https://github.com/waylan/Python-Markdown/commit/044c0f2f61c2e289

Upstream has a large test suite, and the tests are run during build.

If this is approved, I am going to sync python-markdown 2.6-1 from Debian experimental.

Tags: vivid
Revision history for this message
Dmitry Shachnev (mitya57) wrote :
Revision history for this message
Scott Kitterman (kitterman) wrote :

According to the changelog, there are quite a number of new deprecation warnings. Have you investigated if those will affect other packages? I'm inclined to agree with you that we want this in, but I think there should be some assessment of the impact of the deprecation warnings before we decide.

Changed in python-markdown (Ubuntu):
status: New → Incomplete
Revision history for this message
Dmitry Shachnev (mitya57) wrote :

These are just warnings, not actual errors (and these warnings existed in previous release as well, just were upgraded from PendingDeprecationWarning to DeprecationWarning).

The upstream way for removing the features is:

1) PendingDeprecationWarning in release x.y
2) DeprecationWarning in release x.(y+1)
3) functionality removed and no longer works in release x.(y+2)

In this release there were only things that moved from 1) to 2), not from 2) to 3). So nothing to worry about (and the software developers will know that they shouldn't use certain features).

Changed in python-markdown (Ubuntu):
status: Incomplete → New
Revision history for this message
Scott Kitterman (kitterman) wrote :

OK. I was worried about the potential for unguarded raise statements that newly triggered warnings causing problems, but if it's just reclassification from one type of warning to another, I think that's fine.

Please go ahead.

Changed in python-markdown (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Dmitry Shachnev (mitya57) wrote :

This bug was fixed in the package python-markdown - 2.6-1

---------------
python-markdown (2.6-1) experimental; urgency=medium

  * New upstream release.
    - No longer calls logging.captureWarnings on input (closes: #776591).
  * Update debian/watch to point to pypi.debian.net.

 -- Dmitry Shachnev <email address hidden> Fri, 20 Feb 2015 11:00:34 +0300

Changed in python-markdown (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.