[twill] parse_keqv_list not imported, bypass proxy for local addresses
nat.williams at gmail.com
Wed Mar 24 20:37:21 PDT 2010
On Thu, Mar 25, 2010 at 2:24 AM, Marco De Paoli <depaolim at gmail.com> wrote:
> mechanize is hard included in twill, what's the best way to incorporate
>>> mechanize upgrades?
>> Preferred method is to ask Titus to do it ;-)
> Please, Titus... ;-)
> but, why twill doesn't have a package dependency on mechanize?
> easy_install would do the hard work...
so...I had this argument with Titus at Pycon last year. I don't want to put
words in his mouth, but I've kind of come around to his side, so I think I
can lay it out. Basically, twill is largely aimed at the kind of person
that wouldn't even know what easy_install is. That is to say, someone that
is not a python programmer. Obviously this is not to say that twill is not
useful to the seasoned programmer, but it ain't exactly bare metal, and
compromises will be made. Requiring mechanize via setuptools just opens you
up to a whole 'nother layer of potential issues. My opinion at this point is
that if you're asking a question like this, you're probably better off just
I think there's a branch somewhere in the svn repo where I broke out the
built-in mechanize, if that helps you.
>> I do not understand what do you meen with "git"?
>>> (AFAIK mechanize is based on svn
>> Not any more:
> ah, good to know
> mechanize site is not up to date...
>> and what do you mean with "release RSN"?
> ... I found more than one definition, I wasn't sure about it, now it's
> thanks again for the explanations
> P.S. wow John, now I notice you are the mechanize developer... compliments!
> twill mailing list
> twill at lists.idyll.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the twill