Re: Archetypes.public gone?

On Wed, 14 Jun 2006 01:27:02 +0100, Hanno Schlichting  
<plone-+xqiSR9SqHsk+I/[email protected]> wrote:

> Martin Aspeli wrote:
>> Hi,
>>
>> My 3.0 bundle no longer starts up because CacheSetup wants to import
>> Archetypes.public. Did we remove it?
>
> Yes, it was deprecated in AT 1.4, so I removed it this early to see what
> actually breaks and give people some time in advance to update their
> products.

A bigger question is why. I see no practical benefit of deprecating this  
alias and removing it.

>> If so, can we have it back? It's insane to remove it, since soooo many
>> products depend on it. I know someone thought atapi was sexier and more
>> Zope3ish, but I really don't think we can affort to break all those
>> products just for reasons of code cleanliness. Or is there another  
>> reason?
>
> Frankly I don't really care if we undeprecate it in AT 1.4 again and put
> it back for AT 1.5. I just removed it in my general cleaning up to
> remove all deprecated code, it was one of many things.

I agree in principle, but I think this is so widely used (hell, most of my  
products still use it since I was too lazy to figure out which versions of  
Plone and AT had atapi and which had public...) we'd be mad to remove it.

> Other than that we currently maintain two module alias locations for the
> same things, I don't know of any special reasons why it was deprecated.

Even if it just goes in sys.modules, it's pretty cheap and I see no real  
benefit to removing. I mean, there are a lot of other ugly bits in AT we  
should be getting puritan on long before this.

Martin

-- 
"You can just adapt yourself out of it..." // Archipelago sprint 26/04/2006