Skip to content
This repository has been archived by the owner on Jan 2, 2020. It is now read-only.

Make Python entry point configurable #11

Closed
robo9k opened this issue May 25, 2014 · 2 comments
Closed

Make Python entry point configurable #11

robo9k opened this issue May 25, 2014 · 2 comments

Comments

@robo9k
Copy link
Owner

robo9k commented May 25, 2014

Right now the Python entry point is hardcoded to q3py_hello:dllentry.

This needs to be configurable, possibly with environment variables per module (#10).

The documentation needs to explain how to configure the entry point and how libpython searches for the Python module, e.g. PYTHONPATH, virtualenv and activate_this.py etc.

@robo9k robo9k added this to the 1.0.0 milestone May 25, 2014
robo9k pushed a commit that referenced this issue Jun 1, 2014
In preparation for issue #11 the module and method name for
the dllEntry() Python entry point are now read from environment
variables instead of being hardcoded.
@robo9k
Copy link
Owner Author

robo9k commented Jun 4, 2014

33d3e24 changes the behaviour (of 465857c) to use only one environment variable for the entry point.

@robo9k
Copy link
Owner Author

robo9k commented Jun 21, 2014

There is now documentation about how to configure q3py as well.

@robo9k robo9k closed this as completed Jun 21, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant