<div class="gmail_quote">On Thu, Mar 25, 2010 at 2:24 AM, Marco De Paoli <span dir="ltr"><<a href="mailto:depaolim@gmail.com">depaolim@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex"><div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
mechanize is hard included in twill, what's the best way to incorporate<br>
mechanize upgrades?<br>
</blockquote>
<br></div>
Preferred method is to ask Titus to do it ;-)<br></blockquote></div><div><br>Please, Titus... ;-)<br><br>but, why twill doesn't have a package dependency on mechanize?<br>easy_install would do the hard work...<br></div>
</div></blockquote><div><br></div><div>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 using mechanize. </div>
<div><br></div><div>I think there's a branch somewhere in the svn repo where I broke out the built-in mechanize, if that helps you. </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="gmail_quote"><div> <br></div><div class="im">
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex"><div>
I do not understand what do you meen with "git"?<br>
(AFAIK mechanize is based on svn<br>
</div><a href="http://codespeak.net/svn/wwwsearch/mechanize/trunk" target="_blank">http://codespeak.net/svn/wwwsearch/mechanize/trunk</a><<a href="http://codespeak.net/svn/wwwsearch/mechanize/trunk%29" target="_blank">http://codespeak.net/svn/wwwsearch/mechanize/trunk%29</a>.><br>
...)<br>
</blockquote>
<br>
Not any more:<br>
<br>
<a href="http://github.com/jjlee/mechanize" target="_blank">http://github.com/jjlee/mechanize</a></blockquote></div><div><br>ah, good to know<br>mechanize site is not up to date...<br><a href="http://wwwsearch.sourceforge.net/mechanize/#svn" target="_blank">http://wwwsearch.sourceforge.net/mechanize/#svn</a><br>
<br></div><div class="im"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex"><div>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
and what do you mean with "release RSN"?<br>
</blockquote>
<br>
</div><a href="http://www.google.co.uk/search?sourceid=chrome&ie=UTF-8&q=define:RSN" target="_blank">http://www.google.co.uk/search?sourceid=chrome&ie=UTF-8&q=define:RSN</a><div><div></div><div>
<br></div></div></blockquote><div> </div></div><div>... I found more than one definition, I wasn't sure about it, now it's clear<br><br>thanks again for the explanations<br><font color="#888888">Marco</font></div>
</div><br>P.S. wow John, now I notice you are the mechanize developer... compliments!<br>
<br>
<br>_______________________________________________<br>
twill mailing list<br>
<a href="mailto:twill@lists.idyll.org">twill@lists.idyll.org</a><br>
<a href="http://lists.idyll.org/listinfo/twill" target="_blank">http://lists.idyll.org/listinfo/twill</a><br>
<br></blockquote></div><br>