Daniel Nogradi wrote:
> Since I'm starting to use sqlobject right now, if there is a
> similar ORM tool that is comparable but up to date and actively
> developed, that would be an option too. (Things like SQLAlchemy are
> wy to complicated and complex for my needs. :))
Perhaps not really an a
> > To my knowledge, the 0.8.x series is the current line of development, and
> > has
> > made major progress over the previous versions. What makes you think it will
> > be stopped developing? And where does a sqlobject2 come from?
>
> http://www.sqlobject.org/2/
Yes, that's what I meant. The we
"Diez B. Roggisch" <[EMAIL PROTECTED]> writes:
> To my knowledge, the 0.8.x series is the current line of development, and has
> made major progress over the previous versions. What makes you think it will
> be stopped developing? And where does a sqlobject2 come from?
http://www.sqlobject.org/2/
Daniel Nogradi schrieb:
> Hi list,
>
> I get loads of DeprecationWarnings while using sqlobject 0.8.0b1 with
> python 2.5. Does this mean that the sqlobject project is not very up
> to date? Or should I just ignore them and happily use it? In general,
> what's the status of sqlobject, will it be d
Hi list,
I get loads of DeprecationWarnings while using sqlobject 0.8.0b1 with
python 2.5. Does this mean that the sqlobject project is not very up
to date? Or should I just ignore them and happily use it? In general,
what's the status of sqlobject, will it be dropped altogether after
sqlobject2 i