‮rekcäH nitraM‮

Hm, I haven't tested enough probably. But I was Hoping that the default value gets written into the model and thus doesn't change after page creation.

> Nope. Whenever the page gets rebuilt, the default will be recomputed. (Due to Lektor's use of the build cache, the page may not get rebuilt every time the site...

@dairiki Thank you for the explanation. Do you happen to know why the default value doesn't actually get written to the Model? An maybe a slightly different angle: What about...

Because if I understand you right, even overriding the `Type.value_from_raw_with_default()` would not save the value in the model file?

@yagebu yes, I think `initial_value` or `dynamic_initial_value` would be great. I still think that in the long run maybe `default` should be changed to behave this way - but that...

@webknjaz That should be all of the points you brought up - I would be happy for a second round of review.

I think that instead of trying to make the hack in a more estethically pleasing way, it would be better to fix the actual upstream bugs so that the whole...

> I think it would be preferable if this code could do without the writing of `requirements.txt` - instead just read the requirements into a list and install that list...

> In working on #881, I've discovered that installing packages into Lektor's package cache is pretty slow. This means that we should minimize the number package installs we do in...

@dairiki While I do think that splitting out the requirements with `pkg_resources.split_sections()` is probably preferable to parsing the file myself, so I will change that. However, I would really like...