On Fri, Apr 23, 2010 at 10:32 AM, Andreas Jung <li...@zopyx.com> wrote:
> Hash: SHA1
> Brad Allen wrote:
>> On Fri, Apr 23, 2010 at 9:44 AM, Brad Allen <bradallen...@gmail.com> wrote:
>>> On Thu, Apr 22, 2010 at 11:37 PM, Andreas Jung <li...@zopyx.com> wrote:
>>>>> Can this fix be included in the upstream SQLAlchemy DA, so nobody has
>>>>> to monkeypatch it in?
>>>> Sorry - being to busy right now. Please commit the fix yourself and
>>>> someone with Zope checkin permissions in the repos and create a new
>>>> release on PyPI (just tell me the related PyPI user id).
>>> Thank, I'll get started on that. Since I am not sure if that change
>>> will cause problems for anyone else using the SQLAlchemy DA, I guess
>>> I'll start it out as a development release and solicit feedback.
>> To clarify, by development release, I am talking about providing a
>> release which can be installed like this:
> You create a branch on svn.zope.org
>> easy_install SQLAlchemy==dev
> Please can use mr.developer under buildout for svn checkouts.
> I don't want to see dev packages (in general) on PyPI.
>> That would install from a development branch. The normal easy_install
>> would still pull from the most recent release, to avoid disruption and
>> give people time to test. After some time, it could be made to a beta
>> release.
> Sorry but why do you care about easy_install? Serious people use
> buildout. easy_install is for playing around.

Sure, we use buildout where I work. But it relies on setuptools, as
does easy_install. So I was making an example of specifying an egg
using easy_install, but you can also use the same version selection
syntax from a buildout.cfg.

To install the 'dev' version using buildout, it might look something like this:

recipe = zc.recipe.egg
eggs = Products.SQLAlchemyDA==dev

This would allow other users to try out the dev version easily in
their existing buildouts, without having to use svn recipes or
mr.developer. It's important to make it low effort for people in order
get more participation in testing.

>> I've had trouble finding an issue tracker for the SQLAlchemy DA. Would
>> it make sense for me to create one on LaunchPad?
> There is no tracker. You don't need a tracker for such a single issue.

You sound pretty confident that there won't be more issues. I'm glad,
because we want to use SQLAlchemy DA in future production, and have
parts of our app use zsql, while other parts call into the SQLAlchemy
API, possibly from within the same transaction.

I could see the possibility of more issues as we test with different
database platforms like Oracle and MSSQL. Also, I am wondering if any
changes in the DA will be required to support Zope 2.12+.

Even if there is only one ticket to start with, it seems like a good
idea to have an issue tracker.  Would it make sense to use the Zope 2
issue tracker, since this is a component for Zope 2?

Zope maillist  -  Zope@zope.org
**   No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-dev )

Reply via email to