Hi Guys,
I have worked on the 1.1 release and I have all tests working in TG
itself and in the QS template (the default one with SQLAlchemy, with
and without identity)!
In the process I removed all deprecation warnings from SQLAlchemy
0.5.5 about the session_mapper.
At the moment I have just
Florent Aide schrieb:
At the moment I have just replaced the session mapper with the
sqlalchemy.orm.mapper. BUT this means that user code that relied on
the session_mapper behaviour (instanciating the object with arguments,
auto saving, query method on the class) will break.
We could try
*raises hand.
I'm spending a few hours every week on this process. Also, I think we
should have a doc sprint in the near future, as a prelude to TG 2.1a1
release.
cheers.
-chris
On Sep 2, 11:02 pm, Michael Pedersen mjpe...@gmail.com wrote:
Okay, I've been working on these docs quite a bit
I will try to organize the folks from the front range pythoneers to do
a doc sprint.
They are an active group and like sprinting.
I'm going out of town for sept.5-9, so I will not be able to attend
that sprint.
Sept. 18-19 look doable for me tho.
cheers.
-chris
On Sep 1, 10:43 pm, Michael
Hi Florent,
2009/9/3 Florent Aide florent.a...@gmail.com
Hi Guys,
I have worked on the 1.1 release and I have all tests working in TG
itself and in the QS template (the default one with SQLAlchemy, with
and without identity)!
Well done !
In the process I removed all deprecation
I have worked on the 1.1 release and I have all tests working in TG
itself and in the QS template (the default one with SQLAlchemy, with
and without identity)!
This is great news, thanks a lot for your work Florent!
In the process I removed all deprecation warnings from SQLAlchemy
0.5.5
On Thu, Sep 3, 2009 at 9:46 AM, Christophe de VIENNEcdevie...@gmail.com wrote:
Hi Florent,
2009/9/3 Florent Aide florent.a...@gmail.com
Hi Guys,
I have worked on the 1.1 release and I have all tests working in TG
itself and in the QS template (the default one with SQLAlchemy, with
and
raises hand too.
I'll like to expend a couple of hours this weekend getting us a
independent doc release process so we can make this faster and better
and finally see your initial work go live.
On Thu, Sep 3, 2009 at 9:25 AM, perciousch...@percious.com wrote:
*raises hand.
I'm spending a
Florent Aide schrieb:
We could try to mimic the session_mapper behavior (it is documented in
the SQLAlchemy documentation) but I would rather avoid this cruft and
explain how to migrate from the old SQLAlchemy way to the new one...
What do others out there think?
This is nice, but I agree
Christoph Zwerschke schrieb:
This is nice, but I agree with the other Christophs that it at least
should be configurable. The old session_mapper behavior was quite handy,
and the migration can be tedious and error prone if you do not have a
good enough test suite. Actually, the main reason
Well, finally I have committed and pushed the last item for the todo list
for the documentation updates. If you check out the ticket
http://trac.turbogears.org/ticket/2355 you will see this listed as item 2.
Item 1 will be ongoing while the overhaul is happening.
The todo list is 191 items long
11 matches
Mail list logo
