On Sun, Mar 18, 2018 at 4:16 PM, George Fischhof <[email protected]> wrote:
> Hi Jason, > > the status of os and shutil became this because of C functions in > implementation (I got something similar answer before) > ... > > What do you think, what would be a good way to solve this > - add stuff from os to shutil > - add stuff from os and shutil to pathlib > - create a new module on top of os, shutil and pathlib (we could name it > for example filelib > > But...why? It's not clear to me as to how this would actually, you know, *solve* anything. > George > > 2018-03-18 19:43 GMT+01:00 Jason Maldonis <[email protected]>: > >> Surely shutil is a *high* level modules. >>> os is a low level module that shutil builds on. >>> Adding the missing pieces to shutil would make it the place to go to do >>> file operations. >>> Pity its not called filelib. >>> >> >> Gotcha, thank you! shutil being a high level library complicates >> things... So we have two "high-level" libraries (pathlib and shutil) and >> both of them provide different pieces of useful functionality. Maybe I am >> starting to see why this is complicated. Thanks for reading my above reply >> and taking the time to respond. >> >> _______________________________________________ >> Python-ideas mailing list >> [email protected] >> https://mail.python.org/mailman/listinfo/python-ideas >> Code of Conduct: http://python.org/psf/codeofconduct/ >> >> > > _______________________________________________ > Python-ideas mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-ideas > Code of Conduct: http://python.org/psf/codeofconduct/ > > -- Ryan (ライアン) Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else https://refi64.com/
_______________________________________________ Python-ideas mailing list [email protected] https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
