[Grok-dev] Dependencies of megrok.form
steveschmechel at yahoo.com
Fri Apr 10 18:12:43 EDT 2009
The last question I had in that thread unfortunately went unanswered,
regarding how often people use these libraries in real projects.
My suspicion is that they hang around mostly for use in documentation and for legacy purposes.
Unscientific examination of Pypi stats for March 2009 shows:
(top entries only - other entries for context, not to make any statement)
This of course still doesn't reveal how many of these downloads where for "real projects" or just for experimentation. If z3c.widget and/or megrok.form had been closer to grokcore.component, I might conclude that a lot of people use them in their projects.
As it is, it is still unanswered, unless more experienced developers shed some light on the topic.
--- On Fri, 4/10/09, Behrang Dadsetan <bdadsetan at gmail.com> wrote:
> From: Behrang Dadsetan <bdadsetan at gmail.com>
> Subject: Re: [Grok-dev] Dependencies of megrok.form
> To: "steveschmechel" <steveschmechel at yahoo.com>
> Cc: "grok-dev" <grok-dev at zope.org>
> Date: Friday, April 10, 2009, 4:35 PM
> Hi Steve,
> Thank you for your pointers. Adding find-link as you
> mentioned to my
> ~/.buildout/default.cfg made buildout happy. I am sorry, I
> the wrong terms in google and made the wrong assumptions
> searching for a previous case.
> I guess the solution is two fold:
> - People should avoid doing development at 3.30am and
> sending help
> requests around that time (this is mostly pointed to
> - Each howto/sample app should be retested before 1.0. A
> lot of hard
> and nice work was contributed there but I guess howtos just
> software just be tested by someone else than the author. I
> am willing
> to jump in and retest each howto/sample.
> I suggest I log the bugs on https://bugs.launchpad.net/grok
> no matter
> whether they are zope or grok bugs. If they are in grok
> howtos we need
> to at least follow-up on them from our side. We might
> decide to retire
> a library or howto if no one is willing to maintain it or
> it no longer
> works out?
> Thanks again!
> 2009/4/11 Steve Schmechel <steveschmechel at yahoo.com>:
> > 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
> > 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
> >> Hi!
> >> 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
> >> are
> >> supported nowadays OR that I am picking up the
> >> version.
> >> What are the steps for a newcomer like me in this
> >> situation?
> >> 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
> >> supported, does
> >> it make sense to "mark them as
> depricated" in
> >> some way?
> disappear from
> >> pypi? Is
> >> this something we should try to avoid by improving
> >> Thanks for any help!
> >> Kind regards,
> >> Ben.
> >> _______________________________________________
> >> Grok-dev mailing list
> >> Grok-dev at zope.org
> >> http://mail.zope.org/mailman/listinfo/grok-dev
More information about the Grok-dev