Result of nixpkgs-review pr 104401 run on x86_64-linux 1

Result of nixpkgs-review pr 104401 run on x86_64-darwin 1

Lifted to the top level because most users will probably use the cli tool

however, the tool will import the Python code one wrote which imports other modules.

I think its a bad idea to expose this one as top-level attribute and think that it should always be considered as part of a Python environment that has all the modules that one uses in a staticjinja project. Or are you saying one never uses additional Python libraries with staticjinja?

@FRidh I'm saying there's two ways of using this library/program

1. By using it as a dependency in a python environment.
2. By just using the command line tool (staticjinja build), like in most site generators. This might as well be in a larger python project, but in this case staticjinja is treated only as an executable, not as a library. (this is the only way I personally used this project)

Having the executable at the top level facilitates the second, simpler, way

edit: to be clear, in (2), one does not write python code to generate the site, but only jinja templates, which afaik can't import python code by themselves

By just using the command line tool (staticjinja build), like in most site generators. This might as well be in a larger python project, but in this case staticjinja is treated only as an executable, not as a library. (this is the only way I personally used this project)

I understand, but would you argue that one typically does so without any additional Python libraries being used aside from those required by staticjinja?

I'm not sure I understand, could you make an example of using some python library together with staticjinja (the executable), and having the second interfere with the first?

I typically just do something like this (taken from the README):

$ mkdir templates
$ vim templates/index.html
$ staticjinja watch
Building index.html...
Templates built.
Watching 'templates' for changes...
Press Ctrl+C to stop.

Basically I just use it as a simple way to run a template engine. As far as I can see there isn't even a way to use additional python libraries when running it like this.

Okay, I see. I mostly skimmed through the advanced section, thinking that becomes pretty essential considering the basic functionality is so limited.

It depends. If you don't have to load external data (ex. for building simple sites, or for prototyping or reworking a bunch of existing pages) it's surprisingly powerful. If you prefer I can remove the second commit though.

Ping

Oh wait, I see that @FRidh updated it independently in 722c434. Let me rebase...

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.

Result of nixpkgs-review pr 104401 run on x86_64-darwin 1

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.

Result of nixpkgs-review pr 104401 run on x86_64-linux 1