On 29/06/2011 22:46, anatoly techtonik wrote:
On Wed, Jun 29, 2011 at 10:25 PM, Chris Withers<ch...@simplistix.co.uk> wrote:
On 29/06/2011 19:57, anatoly techtonik wrote:
1. more users are familiar with Django templates than with TAL
That an interesting and probably incorrect assertion.
Some proof from my side.
http://www.google.com/trends?q=%22tal+templates%22%2C+%22django+templates%22
Your turn.
Pointless posturing.
Google trends don't provide a way to accurately compare the usage of two
templating languages. The whole Plone community uses TAL, not to mention
the rest of the Zope world, all the people who use chameleon or one of
the other python TAL implementations, not to mention the TAL
implementations in other languages such as Java and PHP.
4. Django templates seems way more simple and no less powerful
That's just plain wrong.
Ok. Then answer the original question. How to override html title
attribute for a subset of PyPI pages?
The root template is likely a macro template, if it hasn't been designed
to allow customising on a per-page basis, you'd need to modify it:
<title metal:define-slot="title"...
Then in the specific template, fill that slot:
<title metal:fill-slot="title"...
Ok. Personal question then - do you support moving PyPI to App Engine?
Absolutely not.
Do you support moving PyPI to other cloud platform?
+0.
I'm in favour of mirrors, how those mirrors are implemented I don't
really care, as long as the http api they expose is consistent and, more
importantly, provided the tools around (ie: setuptools) use them.
If that last issue isn't solved, mirrors are cute and maybe useful in
emergencies where you're prepared to go and manually download packages,
but otherwise they're essentially useless.
cheers,
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Catalog-SIG mailing list
Catalog-SIG@python.org
http://mail.python.org/mailman/listinfo/catalog-sig
