Alberto Valverde wrote:
>> Hi Alberto,
>>
>> Thanks! I applied a slightly modified version of this patch:
>>
>> http://lists.repoze.org/pipermail/repoze-checkins/2008-July/001088.html
>>
>> The code can be checked out from http://svn.repoze.org/repoze.tm2/trunk/ .
>
> Awesome, thanks :)
>
> I'll remove my temporary implementation from rum and use repoze.tm2 now
> instead and tell you how it goes... Then I'll take ata sb at integrating
> it in turbogears2 (this is why I'm cross-posting to tg-trunk)
>
> BTW, where can I tell pkg_resources to pull repoze.tm2 as a distribution's
> requirement from? Are you planning to register it at PyPI like everyone
> else does? ;)
Our release situation is a little complicated right now. There's another
version named "repoze.tm" that is used by "repoze.zope2". The difference
between repoze.tm and repoze.tm2 is that repoze.tm depends not only on
"transaction" but also on all of ZODB ("transaction" is a package that up until
recently always shipped as part of ZODB).
It's appropriate for "repoze.zope2" to depend on ZODB, and thus for it to use
repoze.tm wholesale, not trying to use a standalone "transaction" package. But
it's our intent to retire "repoze.tm" and start to use repoze.tm2 for all of
our
projects. But that requires a couple days worth of development to tease apart
ZODB dependencies our releases of Zope2 so it can use separate "ZODB" and
"transaction" packages. And each version of Zope would need to be tested to
make sure this works, which is probably another day or two worth of effort. We
just haven't done the work.
So, long story short, I've been afraid to release *either* repoze.tm or
repoze.tm2 until I had the time to sort all that out. I'd still rather not
release either to PyPI but I'll go ahead and create a release of "repoze.tm2"
in
an index on dist.repoze.org (which will also contain the transaction package).
- C
_______________________________________________
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev
