by Luc Saffre · in Developers · assigned to Sharif Mehedi

Kurzbeschreibung

Kinder

Kommentare

• 4 Jahre, 1 Monat ago von Sharif Mehedi about #4643 (Make Medico documentation visible) : docs are visible now
• 4 Jahre, 1 Monat ago von Luc Saffre about #4643 (Make Medico documentation visible) : Yep. [url docs.pyinvoke.org/en/stable/concepts/configuration.html the documentation] says that project settings are read *after* user settings, *but* the whole loop is done first for all yaml files and then again for all py files. As it seems.
• 4 Jahre, 1 Monat ago von Luc Saffre about #4643 (Make Medico documentation visible) : Now I could reproduce it. Seems that an ~/.invoke.py is being read after the repository's tasks.py file (i.e. overrides the settings given there instead of just giving default settings)'. Moved blogref_url and blog_root to the tasks.py and removed these settings from my own .invoke.py and now it wor...
• 4 Jahre, 1 Monat ago von Sharif Mehedi Antwort auf Luc Saffre about #4643 (Make Medico documentation visible) : It's visible on gitlab pipeline: [url gitlab.com/lino-framework/medico/-/jobs/2989695230#L579 last pipeline result]. We should probably rename invoke.py to something else.
• 4 Jahre, 1 Monat ago von Luc Saffre about #4643 (Make Medico documentation visible) (1 Antwort) : I can't reproduce this.
• 4 Jahre, 1 Monat ago von Sharif Mehedi about #4643 (Make Medico documentation visible) : having an invoke.py in the project root causes aterlier to fail saying ImportError: cannot import Collection from invoke. It's coming from the line, "from invoke import Collection". the invoke.py shadows the invoke python package.
• 4 Jahre, 1 Monat ago von Luc Saffre about #4643 (Make Medico documentation visible) : The docs should get rendered on [url lino-framework.gitlab.io/medico].