PyLucid CMS Logo

PyLucid v0.10.2 changes...

page message
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
tag cloud ajax | Amazon | Apache | Aptana | backward incompatible | blog | browser | bugfix | ColorMirror | creole | database | dbtemplates | development | django | django-reversion | django-sync | django-sync-server | django-tagging | django-tools | django-weave | documentation | dokumentation | Eclipse | editor | encoding | fastcgi | firefox | firefox sync | formset | generic | git | html | include | IRC | javascript | linux | mysql | pip | plugin | politik | pydev | pygments | pylucid | python | release | screencast | screencasts | security | sicherheit | software | sqlite | standalone | suchmaschine | svn | test | textile | unittest | v0.10 | v0.11 | virtualenv | visible changes | web | webspace

↑ 2012-01-04 - PyLucid v0.10.2 changes...  #

Before 4 months, 2 weeks published by jens.

Changes in v0.10.2: We merged the "context_middlewares" branches with commit ceaf6a52. The goals of this branch are:

  • No work-a-round in template inheritance needed for context middlewares (issues 13)
  • optimized render process (issues 51)

This is not "backward incompatible", but the work-a-round described in issues 13 is obsolete, you can remove it if you have used it.

tags development | documentation | pylucid | v0.10
0 comments for 'PyLucid v0.10.2 changes...':
    there exist no comment for 'PyLucid v0.10.2 changes...'
Leave a comment
tag navi developing

django-processinfo: 5.3 ms of 286.5 ms (1.9%)