Arc Riley wrote: > Grr - you mean trunk *isn't* the head development tree in svn? > Frustrating > in wasted time in duplicated effort. Can you please post this on the > website > so others don't make the same mistake?
trunk is the head dev tree in SVN, but we like to have trunk always passing all tests. 0.6 is very recent and isn't quite passing everything completely so has not been ready for the merge to trunk, but will be soon. the site is in need of updating regarding 0.6's existence but usually people come in and chat on the list or IRC before starting major development initiatives, but sorry, we'll add it. > Yes - we're looking to use sqlalchemy in a Py3-only package set for first > release sometime this week (we can depend on a svn tree for now). Is > basic > ORM, mapping, etc ready in svn rel_0_6? Backwards compatibility isn't > needed since we're implementing new code. ORM and mapping code is the same code as in 0.5. We might remove the ability to say session.flush([list of objects]) but I don't think too much else is planned ORM-wise. > > Yes - we'd be happy to contribute towards getting most/all the tests to > pass > on Py3, especially as needed for our purposes but more generally toward > helping with community migration. > > So 0.6 is planned to have a tarball release specific for Py3, or otherwise > installable for Py3 using setup.py? The 2to3 process is slow and finicky so when 0.6 is fully released, we'll be releasing py2k and py3k tarballs separately. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
