[Grok-dev] Dependencies of megrok.form
steveschmechel at yahoo.com
Fri Apr 10 17:10:30 EDT 2009
This issue has been around for quite a while.
There are work-arounds mentioned in:
and the last comment in:
It would really be nice if someone could poke the right person to get this fixed before version 1.0. Many newbies will probably bonk into this when following the Grok how-to's.
I guess there is resistance to fixing it because it is such a huge library and should be refactored. Unfortunately, I have neither the expertise, time, or Zope repository access to tackle this right now.
You will probably have to work around it by adding
find-links = http://download.zope.org/distribution/
to your buildout.
--- On Fri, 4/10/09, Behrang Dadsetan <bdadsetan at gmail.com> wrote:
> From: Behrang Dadsetan <bdadsetan at gmail.com>
> Subject: [Grok-dev] Dependencies of megrok.form
> To: "grok-dev" <grok-dev at zope.org>
> Date: Friday, April 10, 2009, 2:37 PM
> First of all, I am not sure where to post this issue. I
> apologize if
> this is the wrong place.
> megrok.form (0.2.5) depends on
> z3c.widget (0.1.6) which depends on
> (buildout and
> easy_install can not find it).
> I guess this means that neither z3c.widget nor megrok.form
> supported nowadays OR that I am picking up the wrong
> What are the steps for a newcomer like me in this
> Is it correct to post the issue here? Post on zope-dev? Or
> should it
> rather go as a "bug" on launchpad?
> If I found the above mentioned libraries are no longer
> supported, does
> it make sense to "mark them as depricated" in
> some way?
> pypi? Is
> this something we should try to avoid by improving pypi?
> Thanks for any help!
> Kind regards,
> Grok-dev mailing list
> Grok-dev at zope.org
More information about the Grok-dev