-
-
Notifications
You must be signed in to change notification settings - Fork 108
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
Adding pypandoc-binary for linux #308
Comments
@AbdealiJK thanks for opening this. Since I don't know that much about linux, I had a hard time figuring out a way to make a manylinux binary that included pandoc, since pandoc comes in both dep and tar.gz options, and arm and amd. If you have a suggestion, I would be more than happy to take another look at it :) |
Hi @JessicaTegner The steps for Linux involve:
It's documented at: https://github.com/pypa/manylinux If you would like to try it, I can help debug. |
@AbdealiJK If you look here https://github.com/JessicaTegner/pypandoc/actions/runs/3338893037 This is the latest run I have tried to implemented this with.
Then the next couple jobs, will take care of publishing to gh releases and pypi. |
@JessicaTegner That's awesome. Considering you already have the entire CI setup done up with github actions - I think we can just use the I have created a PR - #309 I found that there are 2 build systems in pypandoc:
It looks like you're in the middle of moving to poetry - so, maybe that gets resolved once you fully move to poetry. |
@JessicaTegner One question though before you do a release - you're aware that there is some issue with pandoc-citeproc when the wheels are getting built ?
I didn't try looking into it cause it was failing in the test CI |
@AbdealiJK that's because since (I think pandoc 2.10) pandoc citeproc has been bundled into the main pandoc executable. |
Just to clarify. This is not a wheel issues... I looked into it, and it's because we use "logger.exception" to print our error message, which results in the stack trace to be printed automatically. A solution to this, would be to change all "logger.exception" in the various platform handlers to warning level instead... Or well, even just info, since it's expected behaviour unless you are using a very old pandoc. |
With #311 out of the way, everything should be done. |
Im good with the changes for wheels :+1 Thanks I will create some PRs for the other cleanups so you can take a look ina while |
Sounds good. Thanks for all your contributions |
It seems I spoke too soon @AbdealiJK take a look at this run: https://github.com/JessicaTegner/pypandoc/actions/runs/3346455236 It seems it refuses to even start the release job at all. Can you take a look at this perhaps? |
Checking |
Created #313 which I THINK will solve the issue. I believe the conditions at ad520d1#diff-944291df2c9c06359d37cc8833d182d705c9e8c3108e7cfe132d61a06e9133ddR73 was not right |
Closing as Linux 64bit wheels are present in pypandoc-binary 1.10 |
Hi, following up from #279
I was just installing pypandoc in a linux setup and thought I could use
pypandoc-binary
but then got the error:
ERROR: Could not find a version that satisfies the requirement pypandoc-binary (from versions: none)
And noticed that wheels for manylinux are not present
Was wondering if there was any reason not to add linux wheels ? Or is that something that can be easily done ?
The text was updated successfully, but these errors were encountered: