[Grok-dev] Dependencies of megrok.form

[Behrang Dadsetan]

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 searched
the wrong terms in google and made the wrong assumptions while
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 myself).

- 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 like
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!

Regards,
Ben.

2009/4/11 Steve Schmechel <steveschmechel at yahoo.com>:
>
> This issue has been around for quite a while.
>
> There are work-arounds mentioned in:
>
> http://www.nabble.com/Re:-The-z3c.widget-is-broken-td22017551.html
>
> and the last comment in:
> http://grok.zope.org/documentation/how-to/automatic-form-generation
>
> 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
>> 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
>>
>> z3c.javascript which can no longer be found on pypi
>> (buildout and
>> easy_install can not find it).
>>
>>
>> I guess this means that neither z3c.widget nor megrok.form
>> are
>> supported nowadays OR that I am picking up the wrong
>> 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 longer
>> supported, does
>> it make sense to "mark them as depricated" in
>> some way?
>>
>> How come a library like z3c.javascript could disappear from
>> pypi? Is
>> this something we should try to avoid by improving pypi?
>>
>> Thanks for any help!
>> Kind regards,
>> Ben.
>> _______________________________________________
>> Grok-dev mailing list
>> Grok-dev at zope.org
>> http://mail.zope.org/mailman/listinfo/grok-dev
>
>
>
>