Philipp S. Sommer

@AnonymouX47, my apologies for coming back to you so late. Is this still an issue with autodocsumm v0.2.13 or can we close this issue?

hey @andy-maier! apologies for the delay. I'd need more information to fix this. Could you please provide a small reproducible example?

@andy-maier I assume that this issue is fixed by #70. could you please give it a try with autodocsumm==0.2.8 and close this issue if this is fixed?

Hey @asmeurer ! Thanks for your input! That does indeed sound like a useful feature :smiley: autosummary does generate these files in a pre-processing step, so outside of the build...

Alright! Thanks for the contribution then already :smiley: Please let me know if and how I can help you and when you start working on it. It shouldn't be too...

Hmm, no idea. Isn't autosummary doing the same with it's generate command? See [here](https://github.com/sphinx-doc/sphinx/blob/7d6d5621fe7fde48545e663c94405efe01503c72/sphinx/ext/autosummary/generate.py#L657). But yes, this seems quite complicated indeed...

thanks for reporting @kloczek! on readthedocs we specify [that the package should be installed prior to building the docs](https://github.com/Chilipp/autodocsumm/blob/master/.readthedocs.yml). Isn't this an option for you instead of manipulating `sys.path`?

thanks for reporting @deckar01! I do have no idea so far what causes this behaviour

Hey @xuhdev ! Thanks a lot for reporting this issue. I think that this should rather be resolved within the autosummary extension, shouldn't it? I saw that you already created...

your approaches sound good! another option for gitlab might be to work with static environments (https://docs.gitlab.com/ee/ci/environments/index.html). You can create CI/CD-variables that are only available for specific environments, and then you...