Welcome!
Welcome to the new TextPress development blog. Until 0.1 is released you can read about the latest code changes here and also discuss them. If you don’t know TextPress (which is very likely as it wasn’t announced anywhere so far) let me introduce you to it :-)
TextPress is a WordPress clone developed in Python with a tight focus on security and extensibility. The code and the installation is separated so you can upgrade multiple blogs in one go once we have a stable release.
If you want to give it a try yourself, head over to #pocoo on irc.freenode.net and give feedback. Google knows the link to the repository ;-) Be warned. So far we don’t recommend TextPress for production environments because there are still some rough edges.
If you are a python developer and interested in the project, here some development details. It’s written for Python 2.4 and higher, uses Werkzeug for the WSGI interface, Jinja as template engine, SQLAlchemy for the database layer and will use Babel for internationalization and localization. So far there are no converters so that’s one of the first things where we need help.
Updates will follow on a regular basis, so stay tuned.
Is there any sort of public code repository, trac instance, or what have you?
Comment by CodeLurker — 2008-02-16 15:18 | # - re
There is a public code repository at dev.pocoo.org as well as a trac.
Comment by Armin Ronacher — 2008-02-16 15:19 | # - re
this is an interesting project. But why did you reimplement the comment parser?
There is one using the bbcode-syntax
Comment by tester — 2008-02-25 05:19 | # - re
Out of curiousity, why just Jinja as a templating engine? I haven’t poked around the code, but is it within the realm of possibility to abstract the out templating system? If you’re reimplementing many of Wordpress’ core features, I could certainly see how it would be trivial for me to rework some of the nicer Wordpress themes into Genshi templates…
Any other python blog software implementing the [Word|Text]press api would be able to reuse any template – Genshi, Jinja, Mako, Kid, Cheetah, yada yada yada, thus users would find themselves with a number of high quality templates very quickly – and they can take their template investment with them if they want to go to another backend.
Just a though…
Comment by Dean Landolt — 2008-03-07 16:08 | # - re
We settled on one templating engine because we want to use the full featureset. For example TextPress tampers with the Jinja AST for the widget system and the plugins extend the load path etc. Additionally the Jinja loader is integrated into the caching layer etc.
While of course it would be possible to support other templating engines as well TextPress would never ship the base templates for all templating engines, neither will the plugins too. This is the main reason why there is just one template engine. If Jinja was the best decision I don’t know, but it’s certainly not the worst.
Regards, Armin
Comment by Armin Ronacher — 2008-03-10 08:26 | # - re
“there are still some rough edges”
Is there a list of these, or the most significant issues aside from what’s in the trac?
Comment by doktora — 2008-04-11 11:16 | # - re