[Python-Dev] Maybe, just maybe, pathlib doesn't belong. (original) (raw)
Random832 random832 at fastmail.com
Tue Apr 12 10:59:05 EDT 2016
- Previous message (by thread): [Python-Dev] Maybe, just maybe, pathlib doesn't belong.
- Next message (by thread): [Python-Dev] Maybe, just maybe, pathlib doesn't belong.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Apr 12, 2016, at 10:52, Sven R. Kunze wrote:
On 12.04.2016 00:56, Random832 wrote: > Fully general re-dispatch from argument types on any call to a function > that raises TypeError or NotImplemented? [e.g. call > Path.missingfunc(os.open, path, mode)] > > Have pathlib monkey-patch things at import?
Implicit conversion. No, thanks.
No more so than radd - I didn't actually mean this as a serious suggestion, but but python does already have multiple dispatch.
> On Mon, Apr 11, 2016, at 17:43, Sven R. Kunze wrote: > I don't get what you mean by this whole "different level of abstraction" > thing, anyway.
Strings are strings. Paths are paths. That's were the difference is.
Yes but why aren't these both "things that you may want to use to open a file"?
> The fact that there is one obvious thing to want to do > with open and a Path strongly suggests that that should be able to be > done by passing the Path to open.
Path(...).open() is your friend then. I don't see why you need os.open.
Because I'm passing it to modfoo.dosomethingwithafile() which takes a filename and passes it to shutils, which passes it to builtin open, which passes it to os.open.
Should Path grow a dosomethingwithmodfoo method?
- Previous message (by thread): [Python-Dev] Maybe, just maybe, pathlib doesn't belong.
- Next message (by thread): [Python-Dev] Maybe, just maybe, pathlib doesn't belong.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]