I would be open to a contribution to do this. But I need it to be easy to push changes to the repo and not difficult to create a release. Today both are very easy to do.

Personally, I'm only have experience with pip as a consumer.

Hi again! Thank you for your message.

I completly understand your concern here.

When I get a minute, I'll create a PR making this possible and we'll see if that suits you

Thanks. I actually went through the process of using the PyPi test site to try out the packaging.

My guess is one PyPi release every major release is reasonable, not every minor update. It probably requires me to copy files into another directory and editing the metadata before using builds and twine`.

Yes, and this is what I'm doing in a PR!

I'll setup the declarative configuration using setuptools so you don't have to install and learn a new tool.

I'll also configure "console scripts" and probably refactor some code so that most of top-level code in the md2pptx file in within a function

I suggest we continue the discussion once the PR is available.

Is refactoring the md2pptx code necessary?

I'm traveling at the moment but hope to look at this over the next few days. I see your PR, Charles, so thanks for that.

I also need to fix Issue 179 in the same timeframe - and call it a release.

Please bear with me.

I'm afraid you're going to have to rework this once I release v5.4.1 with the fix for Issue 179.

Sorry about this.

By the way, how is this supposed to work for people who git clone rather than pip install?

Or just plain take the zip file from a release?

v5.4.1 is out now. Now to go catch a plane home... :-)