On 17 Dez., 03:36, Malcolm Tredinnick <malc...@pointy-stick.com> wrote: > It's very easy: you just don't call it that. Why does it require > "change"?
I have discussed this with the perl naming people here: http://www.nntp.perl.org/group/perl.modules/2008/12/msg63533.html > Choose a different name for it. If you > implement a web server in Perl are you going to call it "Apache::*", if > it does some of the same things as Apache (e.g. using the HTTP > protocol)? No, you're going to find a proper name and then mention in > the docs that it does some of the same things as Apache, or in similar > ways to Apache. That avoids any confusion between your product and the > actual Apache product. It called it that, because it provides a template language like Django, but if this is a problem I will call it something else. Apache is a bad example, since many modules that _use_ Apache are also in the Apache:: Namespace, like Apache::Template and such. So where would you look for a template system to work with your existing Django templates? On 17 Dez., 03:49, "Mike Axiak" <mcax...@gmail.com> wrote: > Hi, > > > 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. > > Um... I know you registered your namespace with CPAN, but as far as I > can tell, CPAN *really* doesn't care if you call it something else > (you don't even need to register a module to have it working on > CPAN...). > > > 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 > > Now this is just wrong. If you call it Template::WhateverIWant and > create the write Makefile.PL, the Makefile will install it into the > right place. There is no place that states A owns A::*. > Well it is not about the module name, but about the list entry. Which has to be the same as the module name, otherwise it won't be found (in the list, not in the search). And in that list there is somewhat of a rule that states A owns A::* https://pause.perl.org/pause/authenquery?ACTION=apply_mod: > Please use this form to apply for the registration of a namespace for a > module you have written or are going to write. The request will be sent off > to the modu...@perl.org people who are maintaining the Modules List. A > registration is not a prerequisite for uploading. It is just recommended for > better searchability of the CPAN and to avoid namespace clashes. You will be > notified when the registration is approved but you can upload immediately, > there's no need to wait for an approval. On the contrary, you are encouraged > to upload immediately. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
