[Catalog-sig] Tab Title customization and Tal to Django/Jinja transition
pydanny at gmail.com
Thu Jun 30 00:00:16 CEST 2011
I'm just going to have to +1,000,000 Chris Withers on everything he says here.
I see ABSOLUTELY no reason to redo PyPI just because of one person
doesn't like how titles and urls are done.
I'm also really leery about hosting it on GAE. That locks PyPI into
one vendor and a proprietary toolset. The inner workings of GAE are
the domain of Google and I would like to think that the main package
repo for Python be 100% open source.
FWIW, Anatoly, there are numerous PyPI clones in Django already. You
are smart. Why not use http://djangopackages.com/packages/p/chishop/
or one of its forks. Then alter it to suit your needs.
On Wed, Jun 29, 2011 at 2:54 PM, Chris Withers <chris at simplistix.co.uk> wrote:
> On 29/06/2011 22:46, anatoly techtonik wrote:
>> On Wed, Jun 29, 2011 at 10:25 PM, Chris Withers<chris at simplistix.co.uk>
>>> 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.
>> 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?
> 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.
> Simplistix - Content Management, Batch Processing & Python Consulting
> - http://www.simplistix.co.uk
> Catalog-SIG mailing list
> Catalog-SIG at python.org
'Knowledge is Power'
More information about the Catalog-SIG