I've fixed this in trunk. I'll release it later to PYPI as soon as I
apply another patch that I have in my backlog for this plugin.
I haven't migrated this and other projects to GitHub yet. I want to do
it some time soon.
On 07/04/11 19:16, Nathan wrote:
> On 2011-04-07, at 9:10 AM, Tres Seaver wrote:
>> On 04/06/2011 11:03 PM, Nathan wrote:
>>> Hopefully this is the right place to post this. The repoze bug
>>> tracker appears to be down so I couldn't post it there, either.
>> I have restarted the roundup instance. Current development of
>> repoze.what has moved from the Repoze SVN repository to Github:
>> New bug reports for repoze.what should likely got to the Github tracker.
>>> I've been testing out SQLAlchemy 0.7b3 in my app and, while it's gone
>>> quite well for the most part, it breaks due to this import in
>>> from sqlalchemy.exceptions import SQLAlchemyError
>>> Apparently .exceptions has been removed in 0.7 (it's now .exc), but
>>> in any case, this import is not used anywhere in this module, and
>>> removing it has no ill effect as far as I can tell.
>>> Is there any chance a new version of this plugin could be released
>>> with this import removed?
>> Our preferred mode for this kind of request is for the reporter to fork
>> the repository, push the requested changes to the fork, and issue a pull
>> request (bog-standard Github interaciton). We need to update the
>> "hacking repoze" docs to indicate the new model for the project moved
>> to Github.
>>  http://docs.repoze.org/hacking/
> I don't see a repository for this plugin on Github, so unless someone wants
> to port it over there, I can just submit a patch from the current SVN
> Thanks for the info, Tres!
> Repoze-dev mailing list
Gustavo Narea <xri://=Gustavo>.
| Tech blog: =Gustavo/(+blog)/tech ~ About me: =Gustavo/about |
Repoze-dev mailing list