Hi Adrian. Many thanks. I guess the thing I am trying to work out is
a project structure to satisfy my wxPython development as well. In any
case I'm going forward with this today and if I have questions, I'll
repost.
It would be nice, structurally if the database wrapping component of
django were modularize in its own library so no need to bring all
django into the distribution to use the db api. It would make it
possible to use it anywhere you need an sql database as opposed to
limiting its use within the full django architecture. Is there anyone
else interested in repackaging the db wrapper into its own library that
could be installed on its own?
I am not sure that this would take a superhuman effort since it would
be more a matter of gathering dependencies and then reconfiguring
somewhat so the admin tool can work with a db configuration as opposed
to a project config, then packaging in a distribution. I am not
completely familiar with django at the moment but am interested enough
in the benefit to help.
I think the overall result would be a wrapper with some really
interesting capabilities to work with or without django and compete
with SQLObject (currently LGPL) as a sensible, general BSD Licensed SQL
wrapper library for python. At the same time, this would likely
generally increase the visibility of django as a side effect.
I don't know, this is only an idea but it would be great to hear from
others. Maybe it should not bother me to install full django in a
wxPython project, but the thought of distributing an application with a
built-in server, templating system, etc when only working with the db
aspect to take advantage of a nice db api seems unnecessary,
particularly with the modular nature of python classes.
Regards,
David
On Wednesday, November 2, 2005, at 10:16 AM, Adrian Holovaty wrote:
On 11/1/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi. I am developing a stand alone desktop application but I like what
django can do as far as wrapping sql database interaction. Can someone
advise of a simple way to use just this part of django outside of
django as a whole.
I am currently working on one project using wxPython and want the
django databse functionality so it is also easier to maintain the sql
afterwards. I still want to be able to use the adminstration tool.
Would I strip certain things out for example to make a light django?
Can someone give me some advice/help on packaging these components as
a
database wrapper.
Hi David,
That should be simple to do. In your wxPython app, just use the Django
database API as normal.
If you're distributing your app, just bundle the Django codebase with
it. Django's BSD license makes that perfectly OK.
Hope this answers your question...Post a response if you have any more
specific concerns.
Adrian
--
Adrian Holovaty
holovaty.com | djangoproject.com | chicagocrime.org
