Hi,
it may be my first message on the list ever, but I wanted to put my 2
cents here.
From the PHP world, Symfony2 introduced a "web installer" system in its
"standard" distribution (which is the core + some fancyness).
To me, it's useless unless you want to attract people from a larger
audience than what the framework is aimed at at first. I personally
don't want some useless (or use-once at best) code to be around my
project, and I don't think it's the role of a developper-oriented piece
of software to provide such things. Of course, a more "newbie-friendly"
may be "nice-to-have", but imho the "core" of a framework should not
provide such thing.
Romain.
On 12/09/2011 18:39, Tom Evans wrote:
On Fri, Sep 9, 2011 at 4:56 PM, Alec Taylor<[email protected]> wrote:
Looks useable.
Anyone interested in working with me to port this to DJango?
Alec, as other people have mentioned, Django is not Drupal. Drupal is
a web application that can be customized using plugins, where as
Django is a python library one can use to create web applications.
With that in mind, 'porting this to django' is nonsensical - PyLucid
uses Django already, and Django is only the framework, not the
project.
The point here is that two different web apps created using Django
could have vastly different requirements and installation steps, where
as Drupal has a single set of steps to go from nothing to installed.
In fact, its quite common to have the same project installed and
running in completely different manners. For instance on our
production servers, all libraries/code/templates, even in house ones,
are installed from our internal package repository (an in house pypi
clone), where as in development, each package is checked out from
subversion in an editable form.
PyLucid is a good example of a project based on django providing
simple and clean installation instructions - although I wouldn't
deploy it quite like that myself, any solution which uses .htaccess is
Bad and Wrong imo*.
(the reason I'm not doing it myself is that I am very new to Python and DJango)
And (not to be too harsh) this is why you are suggesting it. Django is
like a tool, admittedly it's one of those Leatherman style multi tools
that you can use to do almost anything, but it's still a tool for you
to use rather than a base.
Cheers
Tom
* de gustibus non est disputandum
--
You received this message because you are subscribed to the Google Groups "Django
developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
