Conflict with PyPi pymake? about pymake

[jdhughes-usgs]

There is no relationship between PyPI/pymake and modflowpy/pymake other than the name. modflowpy/pymake is not specific to MODFLOW but is primarily used by the authors to compile the various MODFLOW variants.

[markyoder]

Ok, thanks. Would it make sense to call it something else, as to not step on the name pymake? Other than that, it works beautifully, but if PyPi.pymake is installed, the in-script applications will probably fail, and you generally run the risk of corrupting headers, etc. From what I can see, this is a simple matter of changing the name of they pymake directory and then (optionally) modifying the examples/ and of course the documentation. Thoughts?

[jdhughes-usgs]

Yes and the plan is to rename it (maybe mfmakepy) and make it available on PyPI. We haven't done it yet because we use it in most of our continuous integration workflows.

Any good suggestions for a new name?

[markyoder]

Got it. I worked around the problem with a symlink, but I'm interested to integrate it into some other build scripts. If it's pretty general purpose, maybe py-compile ? other-pymake?
Thanks for the info. I'll keep an eye on the project -- happy to help out on a Fork as well.

... or, looking at some of the code (ie, pymake.usgs_program_data.export_json() ), something straightforward like pymake-usgs would work.