On 17 Dez., 03:15, Malcolm Tredinnick <malc...@pointy-stick.com>
wrote:
> Legalities aside, I'd prefer this wasn't done. It will induce confusion
> as there will be some people who think it's associated with the Django
> project. Having a description that says it implements the same
> templating language as XYZ is simply descriptive, but making it clear in
> the name that it's a different project would sit more comfortably with
> me.
Changing the namespace is not that easy, sadly. But I can make a
statement that this has nothing to do with the Djangoproject into the
namespace description. That one can be seen everywhere the name is
displayed.
It would be annoying for any user to write
use
Django::Templates::which::do::not::have::anything::to::do::with::djangoproject
into every script :)
I wanted to call it Template::Django or Template::Like::Django, but
Template::Toolkit blocks the whole Template:: namespace. So the perl
list gurus told me to call it Django::Template
> > P.S.: Since I haven't look at the Django source yet: What the hell
> > does "iriencode" do?
>
> Encodes IRI's, obviously. As documented. :-)
>
> Seriously, it implements section 3.1 of RFC 3987, with the exception of
> international domain name handling (which is consistently not part of
> Django yet, but most likely will be before 1.1).
thanks
Yours,
Maluku (Marc Lucksch)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
