On Oct 22, 12:52 pm, Alberto Valverde <[EMAIL PROTECTED]> wrote: > Mike Orr wrote: > > On 10/21/07, Stou Sandalski <[EMAIL PROTECTED]> wrote: > >> I am running 0.9.6, after some tinkering I found out it was > >> ToscaWidgets that was causing the dependency, sorry. > > >> Is there something out there a bit 'newer' or 'cleaner' than tw that > >> someone can recommend? At least something that doesn't depend on all > >> those packages from PEAK that are 3 years old (PyProtocols, etc.) > > Out of curiosity, is there any inherent problems in packages 3 years old?
No, not really. Except for the TW ones requiring almost manual install (somehow I have never been able to simply do easy_install -U ToscaWidgets)... I always had to do an easy_install on those packages by hand, that is Google for the toscawidgets download directory and then use that for easy_install PyProtocols, etc. > TW doesn't depend on Mighty. However, I've nailed the problem and worked > around it in newest trunk: Apparently Pylons declares a > python.templating.engines entry point, pylonsmighty, which TW tries to > load when initialized [2]. This will cause a DistributionError if Myghty > is not installed. <snip> > [2] Actually, it tries to load all entrypoints by default on init time. > This should be fixed so they're loaded JIT to prevent this kind of errors. Yes that's what I noticed but I couldn't figure out what to do about it. Regards, Stou --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
