john
/
McRogueFace
1
0
Fork 0
Code Issues 52 Pull Requests Projects 1 Releases Wiki Activity

Package mcrfpy without embedded interpreter #70

New Issue
Open
opened 2024-04-11 03:29:27 +00:00 by john · 1 comment
john commented 2024-04-11 03:29:27 +00:00
Owner
Copy Link

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
Author
Owner
Copy Link

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
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
grid_entity_integration
reprs_and_member_names
break_up_ui_h
standardize_font_handling
standardize_vector_handling
standardize_color_handling
standardize_texture_handling
raii_pyobjects
rebase-for-7DRL_Feb-2024
engjam_uicollection
engjam_ui_overhaul
Labels
Clear labels   
Alpha Release Requirement

This issue is a blocker to 0.1 Alpha release of McRogueFace.

  
Bugfix

   
Demo Target

Functionality to demonstrate; Depends on new features, but this issue isn't for writing them.

  
Documentation

   
Major Feature

Significant time and effort required.

  
Minor Feature

Some effort required to create or overhaul functionality.

  
Refactoring & Cleanup

no new functionality, just improving the codebase.

  
Tiny Feature

quick and easy - a few lines or with little interconnection around the codebase

No Label
Alpha Release Requirement
Bugfix
Demo Target
Documentation
Major Feature
Minor Feature
Refactoring & Cleanup
Tiny Feature
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: john/McRogueFace#70
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?