You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pathlib is a more modern way to do path manipulation since Python 3.4. Currently flytekit mixes usage of os.path and pathlib, which makes the code harder to read.
Goal: What should the final outcome look like, ideally?
Using the correspondance table to replace all os.path with pathlib except for some low level string operations that do not have a counterpart in pathlib. For example, os.path.sep.
Describe alternatives you've considered
Replace all pathlib with os.path. This can also prevent the mixed usage of os.path and pathlib but it is not recommended.
Propose: Link/Inline OR Additional context
No response
Are you sure this issue hasn't been raised already?
Yes
Have you read the Code of Conduct?
Yes
The text was updated successfully, but these errors were encountered:
To replace os.path with pathlib in Flytekit, follow the correspondence table to ensure a smooth transition. This will modernize the codebase and improve readability.
Would you like more details on specific replacements or examples of how to implement this change?
Motivation: Why do you think this is important?
pathlib is a more modern way to do path manipulation since Python 3.4. Currently flytekit mixes usage of
os.path
andpathlib
, which makes the code harder to read.Goal: What should the final outcome look like, ideally?
Using the correspondance table to replace all
os.path
withpathlib
except for some low level string operations that do not have a counterpart inpathlib
. For example,os.path.sep
.Describe alternatives you've considered
Replace all
pathlib
withos.path
. This can also prevent the mixed usage ofos.path
andpathlib
but it is not recommended.Propose: Link/Inline OR Additional context
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: