Andreas Klöckner

Thanks for starting this discussion! I'm in principle sympathetic to this. I don't particularly like the `get_local_test_settings_file` thing, I would like to get rid of it. > django-environ Does this...

In particular, that means we shouldn't use `os.path` functions for path processing.

The way I understand path handling in Relate on Windows right now is that one would use `\\` as a path separator (e.g. in Jinja includes), whereas one would use...

In your repos, what do you use for path separators, e.g. when using Jinja: ``` {% from "path1/path2/yaml-macros.jinja" import hw_header %} ``` ? (You may not have any of those...

``` {% from "path1/path2/yaml-macros.jinja" import hw_header %} ``` That's surprising to me, given that [this code](https://github.com/inducer/relate/blob/a97b1273ffb0bf15ea2d56fd4f31d9f52f4b12c7/course/content.py#L653) would try to split the path by `\` and thus try to ask Dulwich...

Thanks! The changes are about support for symlinks in the repo. They should (I think) not affect the behavior I describe one way or another. But since I had to...

As you can probably imagine, I'm not super-excited about this patch: - First, there's no real reason why Jinja in page chunks should behave differently from the way it does...

That sounds like a useful feature.

> but the original license still applies I'd say. What is the original license? A quick skim didn't tell me. > I prefer GPLv3 myself - but either will do...

> Well - the license is right there in the repo: Ah. Didn't realize I was looking at a subfolder. Thanks! > That sounds like a very odd and illogical...