[repoman] platform thoughts
Dan McGee
dpmcgee at gmail.com
Wed Jul 11 18:22:36 EDT 2007
On 7/11/07, Paul Mattal <paul at mattal.com> wrote:
> Jürgen Hötzel wrote:
> > On Sat, Jun 30, 2007 at 01:20:02PM -0400, Paul Mattal wrote:
> >
> >> 3) I would like to use a simple ORM to do *most* things. It's just less
> >> code to get wrong. Obviously, we could still write pure SQL against the
> >> db at any time. What do people recommend for a python ORM that supports
> >> sqlite? SQLObject is around, the django db api is another option (easy
> >> addition of web interfaces later), and there's also SQLAlchemy, I think,
> >> and maybe one or two others. Thoughts?
> >
> > So reposity management will depend on an python web application framework?
> >
> > Will this bring in all the python bloat (which reminds me on broken Gentoo
> > systems due to python updates)? I would prefer a lightweight simple tool,
> > which just the one thing well (repository management) and build other tools
> > (like web frontend) around it.
>
> This had occurred to me, but it will be much easier to put the web
> interface on afterward if we use one ORM which we define now. Given
> that I plan to write a web interface in Django eventually, and the
> main site already uses Django, it seems like a sensible idea.
>
> At least Django is fairly small in things it depends on, unlike some
> other frameworks. It is built mostly on core python, and the
> standard python db-api implementations for the typical dbs.
We can probably make it 'static' as well if need be so we don't have
to worry about the tool being broken. Fully utilizing python means
reuse, and in this case it should help us rapidly speed up development
of the tools we need.
-Dan
More information about the repoman
mailing list