Opened 11 years ago

Last modified 11 years ago

#10423 closed defect

Upgrade Jinja2 to version 2.5.5 (latest upstream) — at Version 2

Reported by: leif Owned by: tbd
Priority: blocker Milestone: sage-4.6.1
Component: packages: standard Keywords: Sphinx download jinja2 spkg
Cc: jdemeyer, timdumol, jhpalmieri, mhansen Merged in:
Authors: Leif Leonhardy Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description (last modified by leif)

The new Sphinx version in Sage 4.6.1.alpha2 (1.0.4, #10118, #10350) requires Jinja2 >= 2.2, while in Sage we currently have version 2.1.1, which triggers undesired downloads during the build.

jinja2-2.5.5.p0 (Leif Leonhardy, December 3rd, 2010)

  • #10423: Upgrade to version 2.5.5, as Sphinx (1.0.4) requires a version >=2.2 (cf. #10350).
  • Some clean-up, dependencies added.


  • Python (>= 2.4)
  • setuptools (or distribute)
  • Pygments (according to 'spkg/standard/deps')
  • docutils (dito, as a note only)

New spkg:

md5sum: 0770c56a50c7c4ab5e926dc45ba4246f jinja2-2.5.5.p0.spkg

Change History (2)

comment:1 Changed 11 years ago by leif

  • Cc timdumol jhpalmieri mhansen added
  • Description modified (diff)
  • Status changed from new to needs_review

Perhaps we could clarify the dependencies; the web page just says Python and setuptools (or distribute).

Also, spkg/standard/deps lacks an explicit dependency on these, instead lists Pygments:

        $(INSTALL) "$(SAGE_SPKG) $(JINJA2) 2>&1" "tee -a $(SAGE_LOGS)/$(JINJA2).log"

There's also:

# For reference and for when the setuptools problem is solved, here
# are the actual dependencies:
# sagenb: python pexpect twisted jinja2 sphinx docutils setuptools
# sqlalchemy: python setuptools
# sphinx: docutils jinja2 pygments
# jinja2: python docutils setuptools
# pygments: python setuptools
# twisted: python python_gnutls setuptools
# zodb: python setuptools

comment:2 Changed 11 years ago by leif

  • Description modified (diff)

Replaced the spkg with a corrected one (version names in SPKG.txt).

Note: See TracTickets for help on using tickets.