-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
MAINT: Fix documentation building on Windows #11656
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
Conversation
OMFG AYKM? |
|
I wish. Cost me more hours than I care to admit today to track it down 😢 |
|
Ready for review/marking for merge when green from my end. Any additional commits should just be updating intersphinx refs |
drammock
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it would be great if you could explain / document why these changes are needed (maybe at next dev meeting?), i.e.
- why is
mne.Dipolenot OK butmne.Epochsis OK? - why are some source filenames being changed to have leading underscores? Is there a rule we should follow regarding this?
That's an excellent question. I'll investigate tomorrow. Maybe something having to do with the import or documentation order would make the
We should have as few public namespaces as possible. I doubt anyone ever did |
|
Okay the Sphinx problem comes down to this: At some point sphinx tries I say we wait for the sphinx people to respond and if there is no workaround in the next few months then we might have to just get rid of the Windows build :( |
|
Not super optimistic on the timeline so I'll close this for now |
I think the root of the SphinxWindows problem is some case sensitivity. If this fixes everything except
mne.Dipoleandmne.label, the fix might be to move our doc of these classes tomne.label.Labelandmne.dipole.Dipole...