/ operator on furl objects

[amoffat]

might be too clever for it's own good. boost::filesystem in c++ uses this technique, and i've always liked it. let me know what you think.

[amoffat]

example:

>>> url = furl("http://www.google.com")

>>> url/"path"/"another_path"/"one_more_path"
furl('http://www.google.com/path/another_path/one_more_path')

>>> print url
http://www.google.com/path/another_path/one_more_path

[gruns]

I think there are better ways to improve conciseness in place of overloaded operators.

One route to ponder is @AlexeyMK's suggestion to process args and kwargs directly. For example, process args like

>>> f = furl('http://www.google.com')
>>> f.path.add('path', 'another_path', 'one_more_path')
>>> f.url
'http://www.google.com/path/another_path/one_more_path'

To me, this is more explicit and straightforward than the overloaded '/' operator.

Here's another example using kwargs for setting fragment query arguments

>>> f = furl('http://www.google.com')
>>> f.fragment.query.add(one=1, two=2)
>>> f.url
'http://www.google.com#two=2&one=1'

So Path and Query objects would each have add(), set(), and remove() methods that process args and kwargs. args and kwargs also play nicely with the unpack operator

>>> argdic = {'one':'1', 'two':'2'}
>>> furl(...).query.set(**argdic)

One downside of adding such args and kwargs functionality to add(), set(), and remove() would be breaking the tenet 'There should be one-- and preferably only one --obvious way to do it.'