Shakeeb Alireza

I've been chipping away at my first max external open-source project, (

), which provides two python3 externals, a more featureful regular max object (

) which provide a two-way interface between python and max; and another (

), a jsextension providing a minimal interface to python via the 

Minus an issue I have no control over, I'm basically getting pretty close and ready to release it to the wild in a pre-alpha state. I have a question about the packaging though:

I've experimented with 3 packaging options for OSX (which is the only one I've implemented so far):

Are options 2 and 3 acceptable for Max. If so do I have to package and embed the library as a Framework? In which directory should I put these in in both cases?

Thanks in advance for any help and or feedback on this question.

I've been chipping away at my  first max external open-source project, (https://github.com/shakfu/py-js), which provides two python3 externals, a more featureful regular max object (py) which provide a two-way interface between python and max; and another (pyjs),  a jsextension providing a minimal  interface to python via the js object.

Embed Python library and .dylib in a Max Package (in the  'support' folder)

Embed Python library and .dylib in the external itself.

I've been chipping away at my  first max external open-source project, (https://github.com/shakfu/py-js), which provides two python3 externa

before-i-release-my-python3-external-a-question-about-packaging

I believe on macOS there soon won't even be a System Python. As it is, that's still at Python 2.

Sorry, when I mean system python, I meant home-brew (-:

It's a great project, I would be happy to learn python in Max/Msp. Are you planning a windows release? Thank you :)

From an initial feature perspective, I'm pretty satisfied with it as a start. But even though it 'works' fine if one only runs it one's own machine, it needs further work to get it working in standalones properly and to get it past Apple's crappy codesign and notarization system.

So, to answer your question. I would like to compile a windows version, or even better, for someone with Max on windows to compile a windows version. It's open-source, python and c and it's cross platform. So no major issues per se. In fact, it will be probably be more straightforward on windows than OS X.

From an initial feature perspective, I'm pretty satisfied with it as a start. But even though it 'works' fine  if one only runs it one's own machine, it needs further work to get it working in standalones properly and to get it past Apple's crappy codesign and notarization system.

So, to answer your question. I would like to compile a windows version, or even better, for someone with Max on windows to compile a windows version. It's open-source, python and c and it's cross platform. So no major issues per se. In fact, it will be probably be more straightforward on windows  than OS X. 

Before I release my python3 external, a question about packaging