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
PostScanner plugins have problems due to compilers being disabled if not used by default post scanning plugin #2496
Comments
Probably because I had totally forgotten post scanner plugins existed. I'll On Thu, Sep 8, 2016 at 11:04 PM Felix Fontein notifications@github.com
|
One way to rescue the optimization is to ask the post scanner plugins which extensions they can find. And offer a way to indicate "I don't know" (by returning |
@felixfontein Yes, if that can be done without breaking compatibility (meaning current behaviour is "I don't know") that works. |
Hmm, I tried to give this a shot, but I found a pretty bad problem. @ralsina, what do you think? Feel free to play around with the branch or to delete it if you don't think this will ever work. |
Nikola only enables compilers which are used by posts found by the standard post scanning plugin (i.e. posts mentioned in
POSTS
andSTORIES
) despite them being mentioned inCOMPILERS
. So if another post scanning plugin tries to add posts which use compilers which appear inCOMPILERS
, but do not appear inPOSTS
andSTORIES
, Nikola won't compile these posts and stop with an error.The main problem are the following lines in
nikola/nikola.py
:If
pp_exts.intersection(v)
is replaced byTrue
, this problem goes away.The text was updated successfully, but these errors were encountered: