Package mcrfpy without embedded interpreter #70

New Issue

john · 2024-04-11T03:29:27Z

john commented

2024-04-11 03:29:27 +00:00

It should be possible to separate the built-in interpreter from the API definitions, build against multiple versions of Python, and distribute wheels.

This isn't how I would deploy McRogueFace for a game, but it would make it a lot more accessible for experimentation.

It would also somewhat betray the "C++ first" philosophy of the engine, but shipping SFML and TCOD would probably keep it pretty snappy.

https://packaging.python.org/en/latest/tutorials/packaging-projects/#choosing-build-backend

It should be possible to separate the built-in interpreter from the API definitions, build against multiple versions of Python, and distribute wheels. This isn't how I would deploy McRogueFace for a game, but it would make it a lot more accessible for experimentation. It would also somewhat betray the "C++ first" philosophy of the engine, but shipping SFML and TCOD would probably keep it pretty snappy. https://packaging.python.org/en/latest/tutorials/packaging-projects/#choosing-build-backend

john added the

Major Feature

Demo Target

labels 2024-04-11 03:29:27 +00:00

john commented

2024-04-11 03:33:32 +00:00

See #54 / #55 for related ideas - in one sense, those two could depend on this. In the other sense, this issue is for the "inside-out" deployment of McRogueFace.

"normal" - McRogueFace executable is the Python interpreter, C++ main loop
"inside-out" - McRogueFace distributed as a package, Python environment has to call some main loop function

That main loop function should have a "short circuit" method in the normal distribution so Python code can freely move between the two kinds of deployment

See #54 / #55 for related ideas - in one sense, those two could depend on this. In the other sense, this issue is for the "inside-out" deployment of McRogueFace. * "normal" - McRogueFace executable is the Python interpreter, C++ main loop * "inside-out" - McRogueFace distributed as a package, Python environment has to call some main loop function That main loop function should have a "short circuit" method in the normal distribution so Python code can freely move between the two kinds of deployment

john referenced this issue from a commit

2025-07-09 12:36:33 +00:00

docs: cancel PyPI wheel task and add future vision for Python extension architecture

john referenced this issue from a commit

2025-07-10 02:52:25 +00:00

Squashed commit of 53 Commits: [alpha_streamline_2]

john added the

priority:tier3-future

label 2025-10-26 00:50:37 +00:00

Sign in to join this conversation.