Is there any chance the package name can be renamed to "openstitching" or something? "stitching" conflicts with our codebase, and python has no good way of handling this.

[JustinMBrown]

I get this is a big ask, but I'm sure there's a fair amount of codebases who have an internal module called stitching that they can't change. I've tried many work arounds, but at this point the cleanest way to solve it is to just copy and paste the entire open stitching codebase into ours which obviously sucks.

Has anyone else run into this?

[lukasalexanderweber]

Is there any chance the package name can be renamed to "openstitching" or something?

no, sorry

Has anyone else run into this?

maybe someone has a good idea for this. git submodules might be a good way to seperate a fork of this repo with an adjusted package name from your codebase.