[zope2-tracker] [Bug 143593] Re: ConflictErrors cause "Shouldn't load state for?"

ChrisW chris at simplistix.co.uk
Thu Apr 8 04:20:48 EDT 2010


Tres Seaver wrote:
>> Yeah, it's just annoying that, on Launchpad, that status also implies 
>> 'we will shortly delete your issue'...
> 
> We do have ancient-but-incomplete bugs for Zope2:
> 
> https://bugs.launchpad.net/zope2/+bugs?field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE

Maybe they're in a different state?

I'm basing my comment on the note at the top of this issue in the web 
interface:

"This bug report will be marked for expiration in 58 days if no further 
activity occurs."

cheers,

Chris

-- 
Simplistix - Content Management, Batch Processing & Python Consulting
            - http://www.simplistix.co.uk

-- 
ConflictErrors cause "Shouldn't load state for?"
https://bugs.launchpad.net/bugs/143593
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.


More information about the zope2-tracker mailing list