Move path.py to omero_ext

[joshmoore]

fix #117

[sbesson]

Immediate thought is that the impact of this change might be fairly large since only in OME, multiple downstream Python components depend on this import.

On the other hand, having the path.py module under the root namespace is certainly a bug which is now becoming critical as we are promoting the installation of this library in a classical Python virtual environment.

My vote goes toward investing into the namespacing effort. Other potential candidates to review might be runProcessor.py runTables.py shellserver.py although some of them might be candidates for migrating under bin/

[joshmoore]

Re-included though ome/omero-scripts#160 will need fixing before we merge (otherwise script PRs will start failing)

[joshmoore]

I think all PRs are now open that would allow this PR to be un-excluded, but waiting on ome/omero-scripts#160 to go green.

cc: @will-moore @sbesson

[sbesson]

From my side with 5.6.0-m2 behind us, no objection to seeing this unexcluded.

[snoopycrimecop]

Conflicting PR. Removed from build OMERO-python-superbuild-push#79. See the console output for more details.
Possible conflicts:

• PR Remove CLI DB integration tests #116 sbesson 'Remove CLI DB integration tests'
  • test/unit/clitest/test_db.py

--conflicts Conflict resolved in build OMERO-python-superbuild-push#80. See the console output for more details.

[sbesson]

As mentioned above, I am in favor of getting this PR merged together with all companion PRs which are implementing a backwards compatible way to deal with the import renaming. This is effectively a breaking change which will need to be documented appropriately in the changelog of this repository. However, due to the interference with upstream path in conda environment, this is largely unavoidable.

Moving forward we will want to review whether switching to the upstream path module is a possibility when time allows.

[sbesson]

Merging and tagging as 5.6.dev6