Familiarisation of using Path.py #1610

[Abhishek-Dev09-zz]

This is an extension of #1610

This give us guide line how deal with path for porting the path #295
a)macOS
b)linux
c)Window
Pypa package- path.py
Outcome- This support both python 2 and 3.
For reference: https://github.com/jaraco/path.py and https://pypi.org/project/path.py
jaraco/path#130

[Abhishek-Dev09-zz]

As dependencies has been added in PR #1639

[Abhishek-Dev09-zz]

@pombredanne : How to use path.py here in path like https://github.com/nexB/scancode-toolkit/blob/develop/src/commoncode/fileutils.py#L84

[Abhishek-Dev09-zz]

@jaraco :Does path.py supports macOS mojave encoding also(APFS)?

[Abhishek-Dev09-zz]

BTW I'm not sure I understand this issue.

Usually it's considered good form for issues to state a problem which can then be solved by a pull request.

Is the problem "scancode uses byte strings, which are no longer supported on python3"? If so, that should probably be the title of this issue.

No,Problem is that i am not able to get it how to use path.py at here https://github.com/nexB/scancode-toolkit/blob/develop/src/commoncode/fileutils.py#L84 .If you know, help me. Its our plan to use path.py to port the path rather than if and else method

[Abhishek-Dev09-zz]

That's... not a bug in scancode. That's more like a forum question.

Issue trackers aren't really for personal todo lists, but if you want to use them like that, please make the description clearer.

Thats why i have written, familiarisation of path.py

[Abhishek-Dev09-zz]

That is a very unclear description. Maybe something like:

Help... not clear how to port src/commoncode/fileutils.py to Path.py

No, this is not about only this file. I want to know how to use path.py in porting the path.

[Abhishek-Dev09-zz]

pombredanne has said that it supports both python 2 and 3. So, it can manage both version and he had tested with pathlib which doesn't work.

[Abhishek-Dev09-zz]

OK, how about

Help... not clear how to port scancode to use Path.py!

which really doesn't sound like something that should be in the issue tracker...?

But hang on, why are you using Path.py? It dropped python2 support a while ago...

It will support python 2 on 11.x series of bugfixes

[Abhishek-Dev09-zz]

OK.

Sorry to give you a hard time about issue style. Now that I kind of understand what's going on, how about

Port path handling to use Path.py

This is an alternative to #1610

I have already mentioned in description that : This is an extension of #1610

[dankegel]

But that was confusing. It's a completely different direction, not an extension.

Maybe I should just accept that I find the description unclear, and not ask you to clarify it further.

[Abhishek-Dev09-zz]

But that was confusing. It's a completely different direction, not an extension.

Maybe I should just accept that I find the description unclear, and not ask you to clarify it further.

Anyways you know how to use path.py ? If yes, Help me

[jaraco]

Does path.py supports macOS mojave encoding also(APFS)?

Yes. Since 2015, I've been developing on macOS with APFS without any issues.

[pombredanne]

@Abhishek-Dev09 re:

Does path.py supports macOS mojave encoding also(APFS)?

Since the key is to support os.fsencode/fsdecode, I do not see any reason why this would not work. You could craft a test for that to verify this BUT if this is not the case that will NOT stop us to use path.py ... instead we would work to update path.py to properly support this.

I do not consider macOS 10.14 as a major OS that would be a show stopper for us.

[pombredanne]

I am closing this for now.