Hi @mahendrark! What did you force-push into this PR yesterday? Usually, it would be better to create an own branch which then merges into an existing PR if you want to add own changes.

Hi @mahendrark! What did you force-push into this PR yesterday? Usually, it would be better to create an own branch which then merges into an existing PR if you want to add own changes.

@smartie2076 , I did not add any changes, just rebased the branch after Sabine merged the last PR. PF taught me to use this technique instead of just merging dev into current branch, when merge conflicts arise.

Hi @mahendrark! What did you force-push into this PR yesterday? Usually, it would be better to create an own branch which then merges into an existing PR if you want to add own changes.

@smartie2076 , I did not add any changes, just rebased the branch after Sabine merged the last PR. PF taught me to use this technique instead of just merging dev into current branch, when merge conflicts arise.

Hmhm, I had to overwrite your rebase as it removed my commits. Weird...

Also weird: When I execute make html I have 16 warnings the first time around, and 0 the second time around. I dont know why that happens.

Also weird: When I execute make html I have 16 warnings the first time around, and 0 the second time around. I dont know why that happens.

oh yeah I experienced this as well when working on open_plan

@Bachibouzouk told me that the compiler or whatever it is that checks the formatting is "smart". So unless you make changes and run it, it wont show you the warnings/errors again if you run make html immediately without changing code

the errors will still be there! This drove me crazy some time ago :/

Hi @mahendrark! What did you force-push into this PR yesterday? Usually, it would be better to create an own branch which then merges into an existing PR if you want to add own changes.

@smartie2076 , I did not add any changes, just rebased the branch after Sabine merged the last PR. PF taught me to use this technique instead of just merging dev into current branch, when merge conflicts arise.

Hmhm, I had to overwrite your rebase as it removed my commits. Weird...

oh-oooh
I have no idea what happened. I rebased like how I do normally on every branch.
I do remember that I saw only commit when I opened this PR for reviewing. Just the one "Use version number in RTD ". That why it has me as co-author.. strange indeed.

I will run make html on this branch and post how many warnings/errors I run into

I will run make html on this branch and post how many warnings/errors I run into

Great, thanks!

@smartie2076

I have 16 errors still when I run make html. I guess you can merge it and I can add the task of fixing them to #646 because it is dealing with RTD anyway

@smartie2076

I have 16 errors still when I run make html. I guess you can merge it and I can add the task of fixing them to #646 because it is dealing with RTD anyway

That would be perfect, thank you! I also think that my PC is buggy in the compilation of those errors. I wonder if there is also a pytest that can check that the RTD compilation runs though without any errors/warnings, so that we can make sure that we never again have to deal with that many bugs at once...

I have 16 errors still when I run make html.

Note: The warnings regarding autosummary are fixed for me after the second code execution. The changes in conf.py are the ones that should have fixed them...