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
Currently the current path.py and the older forked-path python modules are both called path. There is a naming conflict if they are both installed on the system and will cause issues.
It's been suggested that on installation (through setup.py) that a check for forked-path is made, and if found, to abandon the installation and inform the user to remove the forked-path first.
Original report (archived issue) by Eric Roberts (Bitbucket: ericr86, GitHub: ericr86).
Currently the current
path.py
and the olderforked-path
python modules are both calledpath
. There is a naming conflict if they are both installed on the system and will cause issues.It's been suggested that on installation (through
setup.py
) that a check forforked-path
is made, and if found, to abandon the installation and inform the user to remove theforked-path
first.See Issue #50
The text was updated successfully, but these errors were encountered: