intercept / intercept-python

A Python binding library for Intercept

intercept-python

A Python binding library for Intercept

intercept-python's Issues

Using system interpreter

Would it be possible to use the system interpreter and using named pipe communication (or similar) to the intercept process?
This would remove the versioning complexity and would only require the PYTHON system path variable to be set, this could also be overridden on a per plugin/mod basis if specific versions are required (multiple python versions in the same arma installation).
I am not sure about the complexity or performance implications of this approach.

Styling/coding standards

Which coding standards/PEP guides are you planning to adhere to.
As this is a python library aimed at python users(presumably) the PEPs would be a good place to start.

Also when implementing the classes there are a couple options regarding the OOP interface as I see it:

1. literal translations so getPos player becomes player.getPos(). or player.get_pos()
2. @property decorator to wrap the calls to the DLL to the user so that getPos player becomes player.pos , and player setPos [a,b,c] becomes player.pos = [a,b,c].
3. Both of the above, having one approach call the other for example. This illustrates both approaches, and is therefor less pythonic ("one way to do something").

     class RV_Object(object):
        def __init__(self):
           # todo
           pass

        @property
        def pos(self)->tuple:pass

        @pos.setter
        def pos(self, pos:tuple)->None:pass

        def get_pos(self)->tuple: pass # todo

        def set_pos(self, pos:tuple)->None: pass # todo

Sitrep?

Hello,
What is the current status of this project, are we still waiting for:
intercept/intercept#110 as mentioned in intercept/intercept#168?

cheers
Lonja

Compile Python static from source with CMake

This buildfile seems to work.
Needs changes to work with python 3.6 and remove options as they arent requiered if we build it just for our plugin.