On Feb 8, 3:46 pm, Blaise Laflamme bla...@laflamme.org wrote:
Hi jonathan,
feel free to modify the sphinx theme and send a pull request. Actually
older versions like 1.1, 1.2, etc, are not out-of-date but up-to-date with
those versions. There are the latest and the development one that
No the new theme is not online, I've been just playing with different ideas
before starting the public project. The current theme is
here: https://github.com/Pylons/pylons_sphinx_theme
Do you attend pycon this year?
On Saturday, 9 February 2013 13:56:42 UTC-5, Jonathan Vanasco wrote:
On Feb
On Feb 9, 2:21 pm, Blaise Laflamme bla...@laflamme.org wrote:
No the new theme is not online, I've been just playing with different ideas
before starting the public project. The current theme is
here:https://github.com/Pylons/pylons_sphinx_theme
Do you attend pycon this year?
Sadly no, I
what controls how the pyramid docs get built and stored onto
doc.pylonsproject ?
looking at the github source (
https://github.com/Pylons/pyramid/tree/master/docs
) it looks to me like only the current docs are in master, and the
older ones are built off misc releases
the reason why i ask, is
We are limited by what readthedocs is actually capable of doing. It doesn't
support branch aliases right now, so unless we make a stable branch that
we merge with 1.4-branch every time we update, we make do with latest.
Same issue with the major.minor -branch issue.
If someone wants to add alias
Hi jonathan,
feel free to modify the sphinx theme and send a pull request. Actually
older versions like 1.1, 1.2, etc, are not out-of-date but up-to-date with
those versions. There are the latest and the development one that reflects
the current stable and development versions of Pyramid. A
And tags to v1.4, yes :)
On Fri, Feb 8, 2013 at 10:49 PM, Tshepang Lekhonkhobe tshep...@gmail.comwrote:
Would it solve the problem if the branches were simply renamed, from
e.g 1.4-branch to 1.4?
On Fri, Feb 8, 2013 at 9:23 PM, Michael Merickel mmeri...@gmail.com
wrote:
We are limited by
