-
Notifications
You must be signed in to change notification settings - Fork 34
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
alectryon.minimal
and a no-coq-serapi
use-case
#60
Comments
This is an issue with relative imports: it will happen if
Not too hard, and you can still get a bit of functionality by usign |
Clement, Thanks for your quick replies regarding my issue/feature request. Unfortunately I was ill last week which has thrown a wrench in some of my other work-plans for August; I don't think that I will have a chance to test this until later this week (or next week). With that being said, I will be sure to respond as soon as I get my hands on that branch! ~Jasper |
No worries at all. Hope you got better! |
Thanks for the well wishes; I am indeed feeling better now. I spent some time today trying to get things working but I've continued to run into problems. In particular, before I was able to test out your branch I wanted to ensure that I had the most up-to-date version of Alectryon, so I switched from
The first half of the path ( I've noticed this warning in the past but I could never trace it down (and I didn't get around to opening a bug report). However, this is now becoming a blocker for me w.r.t testing out your other changes. Do you know why/where we prepend the |
Wild guess: could it be rocq-archive/coq-serapi#249 ? In the meantime, you could turn off the sphinx feature that treats warnings as errors (remove |
That does look related; we'll probably wait a bit to bump serapi, but removing that |
It's expected: errors and warnings produced by Alectryon were not integrated into Docutils and Sphinx' error-reporting system until very recently (#57) |
Clément, After removing the
Unfortunately, when I try to use
Do you have any ideas why this error might be occurring? Fwiw, I use the normal A few other related items:
|
I will double-check.
Ah! You don't need to do that; you can just drop
Soon ^^ I was waiting for feedback from @gmalecha since part of this patch was for his use case, but I'm ready to move ahead.
I'm wary of adding yet another configuration mechanism. But fortunately we can simplify things a bit. Would the following work, in your sphinx config?
You already have the fix, it's
Definitely not. |
Found and fixed, thanks. |
I have merged the gh-60 branch, with an updated changelog. |
Thanks for your thoughtful response to my (long) message and for merging |
Yep. But beware: the |
Clément,
During Coq bumps at work, we sometimes experience breakages to our documentation caused by delays in corresponding SerAPI bumps on opam. I'm working to engineer a solution locally and I was initially planning to use
alectryon.minimal
, but I've been running into some problems. In particular, if I try to replacealectryon/alectryon.py
withalectryon/alectryon/minimal.py
in mySphinx
conf.py
file (edit: I changed which pyhon script I invoke forAlectryon
within myMakefile
), I end up with the following error:Am I using this file in the wrong way or has this functionality fallen somewhat out of date?
On a related note, how easy would it be for you to add a switch to the regular
alectryon.py
infrastructure which disables calls toserapi
while retaining the regular alectryon functionality? In reality, it seems like we're more interested in a way to avoid breakages caused by bump-lag withserapi
; we don't mind very much if we temporarily lose proof movies (if we're able to choose when we want to turn them off).The text was updated successfully, but these errors were encountered: