This commit fixes a papercut in nixos-rebuild where people wanting to
switch to a specialisation (or test one) were forced to manually figure
out the specialisation's path and run its activation script - since now,
there's a dedicated option to do just that.
This is a backwards-compatible change which doesn't affect the existing
behavior, which - to be fair - might still be considered sus by some
people, the painful scenario here being:
- you boot into specialisation `foo`,
- you run `nixos-rebuild switch`,
- whoops, you're no longer at specialisation `foo`, but you're rather
brought back to the base system.
(it's especially painful for cases where specialisation is used to load
extra drivers, e.g. Nvidia, since then launching `nixos-rebuild switch`,
while forgetting that you're inside a specialisation, can cause some
parts of your system to get accidentally unloaded.)
I've tried to mitigate that by improving specialisations so that they
create a dedicated file somewhere in `/run/current-system` containing
the specialisation's name (which `nixos-rebuild` could then use as the
default value for `--specialisation`), but I haven't been able to come
up with anything working (plus it would be a breaking change then).
Closes https://github.com/NixOS/nixpkgs/issues/174065
Upstream added a `monai[ninja]` install option and a corresponding
`ninja = ` in `setup.cfg`, which broke a previous hack around
`setuptools` not detecting `ninja` correctly.
Split package into top-level Python library.
We need to propagate it just like any other package, otherwise
dependents cannot detect it during installation.
The __init__.py collide since it uses old-style namespaces so we get rid
of those. In the future we may need to extend the namespaces.
This was enough for my dependency opencensus-ext-azure.
Having it as a top-level Python is just common practice; there is no
good reason not to.
As a companion to #210873, this change adds some of the builtin plugins
and themes, that generally ship with wordpress, so that consumers can
explicitly opt into including them in their wordpress derivation.
It fails, because the examples require python3.10 to be executed.
```
WARNING: examples for 3.10+ requires python 3.10. They won't be executed
Traceback (most recent call last):
File "/build/source/docs/build/main.py", line 31, in <module>
sys.exit(main())
File "/build/source/docs/build/main.py", line 27, in main
return exec_examples()
File "/build/source/docs/build/exec_examples.py", line 354, in exec_examples
versions.extend(populate_upgraded_versions(file, file_text, lowest_version))
File "/build/source/docs/build/exec_examples.py", line 294, in populate_upgraded_versions
new_file.write_text(upgraded_file_text)
File "/nix/store/9pilxd2znfsj64ybyg8lmgql9vy3fq4g-python3-3.9.16/lib/python3.9/pathlib.py", line 1285, in write_text
with self.open(mode='w', encoding=encoding, errors=errors) as f:
File "/nix/store/9pilxd2znfsj64ybyg8lmgql9vy3fq4g-python3-3.9.16/lib/python3.9/pathlib.py", line 1252, in open
return io.open(self, mode, buffering, encoding, errors, newline,
File "/nix/store/9pilxd2znfsj64ybyg8lmgql9vy3fq4g-python3-3.9.16/lib/python3.9/pathlib.py", line 1120, in _opener
return self._accessor.open(self, flags, mode)
FileNotFoundError: [Errno 2] No such file or directory: '/build/source/docs/.tmp_examples/upgraded/dataclasses_default_schema_3_9.py'
make: *** [Makefile:118: docs] Error 1
```
Patryk Wychowaniec