On 12 October 2012 20:39, Georg Brandl <span dir="ltr">&lt;<a href="mailto:g.brandl@gmx.net" target="_blank">g.brandl@gmx.net</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

Am 12.10.2012 18:27, schrieb Ethan Furman:<br>
<div class="im">&gt; Georg Brandl wrote:<br>
&gt;&gt; Am 12.10.2012 14:45, schrieb Blake Hyde:<br>
&gt;&gt;&gt; I&#39;m a Python developer rather than a developer of Python, but I&#39;d like to ask a<br>
&gt;&gt;&gt; question about this option (and implicitly vote against it, I suppose); if you<br>
&gt;&gt;&gt; specialize a method name, such as .pathjoin, aren&#39;t you implying that methods<br>
&gt;&gt;&gt; must be unambiguous even across types and classes?  This seems negative.  Even<br>
&gt;&gt;&gt; if .join is already used for strings, it also makes sense for this use case.<br>
&gt;&gt;<br>
&gt;&gt; Of course different classes can have methods of the same name.<br>
&gt;&gt;<br>
&gt;&gt; The issue here is that due to the similarity (and interchangeability) of path<br>
&gt;&gt; objects and strings it is likely that people get them mixed up every now and<br>
&gt;&gt; then, and if .join() works on both objects the failure mode (strange result<br>
&gt;&gt; from str.join when you expected path.join) is horribly confusing.<br>
&gt;<br>
&gt; I don&#39;t understand the &quot;horribly confusing&quot; part.  Sure, when I got them<br>
&gt; mixed up and ended up with a plain ol&#39; string instead of a really cool<br>
&gt; Path it took a moment to figure out where I had made the error, but the<br>
&gt; traceback of &quot;AttributeError: &#39;str&#39; object has no attribute &#39;path&#39;&quot; left<br>
&gt; absolutely no room for confusion as to what the problem was.<br>
<br>
</div>&quot;no attribute &#39;path&#39;&quot;?  Not sure where that exception comes from.<br>
This is what I meant:<br>
<br>
&gt;&gt;&gt; p = Path(&#39;/usr&#39;)<br>
&gt;&gt;&gt; p.join(&#39;lib&#39;)<br>
Path(&#39;/usr/lib&#39;)<br>
<br>
&gt;&gt;&gt; p = &#39;/usr&#39;<br>
&gt;&gt;&gt; p.join(&#39;lib&#39;)<br>
&#39;l/usri/usrb&#39;<br></blockquote><div><br></div><div>I don&#39;t know about you, but I found that so horribly confusing I had to check the output. I&#39;m just not used to thinking of str.join(str) as sensible, and I could not for the life of me see where the output &#39;l/usri/usrb&#39; came from. Where was &quot;lib&quot;?</div>

<div><br></div><div>I might just have been an idiot for a minute, but it&#39;ll just get harder in real code. And I&#39;m not the worst for stupid mistakes: we wan&#39;t newbies to be able (and want) to use the built in path modules. When they come back wondering why </div>

<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><font face="courier new, monospace">homepath.join(&quot;joshua&quot;).join(&quot;.config&quot;)</font></blockquote>

returned<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><font face="courier new, monospace">&#39;.j/homeo/homes/homeh/homeu/homeacj/homeo/homes/homeh/homeu/homeaoj/homeo/homes/homeh/homeu/homeanj/homeo/homes/homeh/homeu/homeafj/homeo/homes/homeh/homeu/homeaij/homeo/homes/homeh/homeu/homeag&#39;</font></blockquote>

<div>we are going to have a problem.</div><div><br></div><div>So I agree with you [Georg Brandl] here. I would even rather .pathjoin/.joinpath than .join despite the utterly painful name*.</div><div><br></div><div>* As others have stated, if you like it why not .strjoin and .dictupdate and .listappend?</div>

</div>