Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Newsgroups: comp.lang.python
Date: Sat, 13 Oct 2012 15:24:04 -0700 (PDT)
In-Reply-To: <mailman.2132.1350153223.27098.python-list@python.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=173.88.33.244; posting-account=s5n-HgoAAAADkPp3Xa9skJeRDkBou06u
References: <634c9dca-e64d-40c6-b9d5-cf04a86a220a@googlegroups.com> <mailman.2116.1350137553.27098.python-list@python.org> <4c7a82ca-de0c-4b8b-a128-9ecd1b4c8b31@googlegroups.com> <mailman.2124.1350146902.27098.python-list@python.org> <5f18f5d1-1442-4a10-922c-783dc6ddf657@googlegroups.com> <mailman.2132.1350153223.27098.python-list@python.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Subject: Re: Feedback on my python framework I'm building.
From: nbvfour@gmail.com
To: comp.lang.python@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: python-list@python.org
Precedence: list
Message-ID: <mailman.2150.1350167052.27098.python-list@python.org>
Lines: 34
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:31226

On Saturday, October 13, 2012 2:33:43 PM UTC-4, Chris Angelico wrote:
>=20
> Nice theory, but this is the bit that I fundamentally disagree with.
> Forcing programmers to work in one particular style is usually not the
> job of the language/framework/library. That should be up to the
> programmer, or at least the local style guide.=20

Have you ever read the zen of python? "Theres only one way to do it" is a c=
ore motto of the python language. In my opinion, this is the most important=
 aspect of python and is what makes python so much better than PHP and perl=
 and all the other "do it however you want, the more convoluted and obfusca=
ted the better!" languages.

> I do like your plan of
> having identical interfaces to the same functionality (your example of
> web-based and command-line is particularly appealing to my personal
> tastes), but the same can usually be achieved with a well-built
> library. In fact, all you need to do is have your model as a simple
> Python module, and then the view and controller call on its functions.
>=20
> What does your framework offer over a basic system like that?

This "well built library" you mention basically describes my framework. You=
 write a model method/function that takes data and then returns data. All g=
iotto does is extract that data from the controller, pass it on to the mode=
l, then take the output of the model and pass it in to the view. You write =
the view, you write the model. Giotto provides the API for making al this h=
appen. Giotto doesn't care if your model calls Postgres or Mysql or Redis o=
r RabbitMQ, thats not of any concern to the framework.

The advantage of this is that the framework can 'mock' out the model layer =
very easily. For instance, your front end designers can work on the HTML wi=
thout needing to run postgres, and the backend developers can work on the b=
ackend through the command line.