megrok.rdb conflict with zope.sqlalchemy

[David Pratt-5]

Hi. I have run into this issue with megrok.rdb.  Changes were made to
zope.sqlalchemy for days ago bumping the version so it will not build
with 0.5.0beta1

Error: There is a version conflict.
We already have: SQLAlchemy 0.5.0beta1
but zope.sqlalchemy 0.3 requires
'SQLAlchemy>=0.4.7,!=0.5.0beta1,!=0.5.0beta2'.

Many thanks.

Regards,
David
_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev

[Toni Mueller-4]

Hi,

On Sat, 02.08.2008 at 18:41:51 -0300, David Pratt <fairwinds.dp@...> wrote:
> Hi. I have run into this issue with megrok.rdb.  Changes were made to  
> zope.sqlalchemy for days ago bumping the version so it will not build  
> with 0.5.0beta1

I guess there's a reason, and, btw, you're probably well advised to
upgrade, anyway. You might be interested in this:

"0.3 (2008-07-29)

Bugs fixed:

    * New objects added to a session did not cause a transaction join,
      so were not committed at the end of the transaction unless the
      database was accessed. SQLAlchemy 0.4.7 or 0.5beta3 now required.
"

(from PYPI).


I'd say, if you're in a hurry, downgrade to zope.sqlalchemy 0.2.



Kind regards,
--Toni++
_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev

[Martijn Faassen-2]

Hey,

Toni Mueller wrote:
> On Sat, 02.08.2008 at 18:41:51 -0300, David Pratt <fairwinds.dp@...> wrote:
>> Hi. I have run into this issue with megrok.rdb.  Changes were made to  
>> zope.sqlalchemy for days ago bumping the version so it will not build  
>> with 0.5.0beta1
[snip]
> I'd say, if you're in a hurry, downgrade to zope.sqlalchemy 0.2.

I just investigated this.

Yes, this seems to be the best approach right now. The release of
SQLAlchemy 0.5beta3 should've happened a while ago, but it didn't, and
this is what is required to get out of this with a newer version of
zope.sqlalchemy...

I'll drop Make Bayer a mail about this.

Regards,

Martijn

_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev

[Toni Mueller-4]

Hi,

On Mon, 04.08.2008 at 13:52:16 +0200, Martijn Faassen <faassen@...> wrote:
> Yes, this seems to be the best approach right now. The release of  
> SQLAlchemy 0.5beta3 should've happened a while ago, but it didn't, and  
> this is what is required to get out of this with a newer version of  
> zope.sqlalchemy...
>
> I'll drop Make Bayer a mail about this.

seems he has listened, since 0.5b3 is announced on the web page today.


Kind regards,
--Toni++
_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev

[Martijn Faassen-2]

Hey,

Toni Mueller wrote:
> On Mon, 04.08.2008 at 13:52:16 +0200, Martijn Faassen <faassen@...> wrote:
>> Yes, this seems to be the best approach right now. The release of  
>> SQLAlchemy 0.5beta3 should've happened a while ago, but it didn't, and  
>> this is what is required to get out of this with a newer version of  
>> zope.sqlalchemy...
>>
>> I'll drop Make Bayer a mail about this.

Oops, "Mike Bayer" of course.

> seems he has listened, since 0.5b3 is announced on the web page today.

Yes, he was busy working on it already when I mailed him. :)

The megrok.rdb tests run with 0.5b3 too - I just verified it.

Regards,

Martijn

_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev