Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A python package on the way? #134

Open
pissalou opened this issue Jan 15, 2025 · 5 comments
Open

A python package on the way? #134

pissalou opened this issue Jan 15, 2025 · 5 comments

Comments

@pissalou
Copy link

Hello Jean-Michaël,
I noticed the recent addition of python bindings to the project. Is your intention to also build python packages in github actions and publish them to pypi.org? I think that would be of great value and would happily look into making a workflow for it if you agree.

@jcelerier
Copy link
Member

Hello ! Yes, and help for the GH workflow especially for submitting to PyPI would be amazing!

@jcelerier
Copy link
Member

I'm currently adding a GH workflow in #140

@jcelerier
Copy link
Member

python workflow merged !

@pissalou
Copy link
Author

pissalou commented Mar 5, 2025

Hello Jean-Michael, I have tried to import the pyd file generated by the workflow on windows 10 but it is failing:
`Python 3.13.2 (tags/v3.13.2:4f8bb39, Feb 4 2025, 15:23:48) [MSC v.1942 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

import sys
import os
import dlltracer
os.add_dll_directory('C:\Windows\System32')
<AddedDllDirectory('C:\Windows\System32')>
with dlltracer.Trace(out=sys.stdout):
... import pylibremidi
...
LoadLibrary C:\Windows\System32\kernel.appcore.dll
LoadLibrary C:\code\jambuddy\pylibremidi.pyd
LoadLibrary C:\Windows\System32\winmm.dll
Failed \Device\HarddiskVolume3\Windows\System32\winmm.dll
Failed \Device\HarddiskVolume3\code\jambuddy\pylibremidi.pyd
Traceback (most recent call last):
File "", line 2, in
import pylibremidi
ImportError: DLL load failed while importing pylibremidi: The specified module could not be found.`

I suspect it is because the project is compile with --config Debug and I do not have the vc++ debug DLLs, I will try again with the --config flipped to Release to confirm this hypothesis.

@jcelerier
Copy link
Member

this could definitely be a cause indeed, the MSVC toolchain does not support mixing debug and release DLLs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants