gasp-dev team mailing list archive

[Jeff Elkner <jeff@xxxxxxxxxx>]

Let's defer this discussion until later (a good topic for a 0.4 release).
We wanted api.py and backend.py because in pygame it made it *much* easier
for beginners to look at how the api behavied without having to read through
pygame details.  If that is no longer the case, I'll be open to the change
you suggest, Luke, but I don't want to rush into it and I want to hear what
Jamie thinks first.

Thanks!

jeff

On Thu, Aug 20, 2009 at 7:51 AM, Luke Faraone <luke@xxxxxxxxxx> wrote:

> Hi,
>
> As I was looking through the GASP distribution, I was wondering if the
> separation of GASP into separate frontend and backend .py files was doing
> more harm than good. Global variables, initialization of objects occurring
> outside of __init__, etc, are all things that, while it works, impede
> readability and make it harder for students to understand GASP.
>
> If needed, we can prepend private/internal interfaces with _ and *very
> private* interfaces with __ per PEP 8<http://www.python.org/dev/peps/pep-0008/>
> .
>
> Granted, the code works well. I'd just like to improve the maintainability
> :)
>
> --
> Luke Faraone
> http://luke.faraone.cc
>