| 8 Nov 2024 |
 hexa | which otoh means that when parsed by a yaml 1.1 parser will lead to unexpected results | 18:02:23 |
| hexa | $ cat test.json
{
"time": "22:30:00"
}
$ json2yaml test.json test.yaml
$ cat test.yaml
time: 22:30:00
$ python3
Python 3.12.7 (main, Oct 1 2024, 02:05:46) [GCC 13.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import yaml
>>> yaml.safe_load(open("test.yaml"))
{'time': 81000}
>>>
| 18:02:34 |
| hexa | $ cat test.json
{
"enable": "on",
"disable": "off"
}
$ json2yaml test.json test.yaml
$ cat test.yaml
enable: on
disable: off
$ python3
Python 3.12.7 (main, Oct 1 2024, 02:05:46) [GCC 13.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import yaml
>>> yaml.safe_load(open("test.yaml"))
{'enable': True, 'disable': False}
| 18:02:50 |
 emily | IIRC YAML 1.2 isn't that widely-adopted (though maybe that's changed?). is there a remarshal flag to use 1.1? | 18:03:31 |
| hexa | I'm contemplating whether to provide the remarshal package in an old version for yaml 1.1 support | 18:03:44 |
| hexa | and have a toggle for the formatter that switches the package around | 18:03:56 |
| emily | I think we shouldn't change the output of those kinds of things in general except for clear bugfixes. even making escapeShellArg omit quotes when unnecessary broke tons of stuff across the entire ecosystem in and out of tree | 18:04:12 |
| hexa | no, they switched from pyyaml to ruamel-yaml, which is a clean 1.1 to 1.2 swap | 18:04:13 |
| emily | ah | 18:04:21 |
| emily | https://github.com/remarshal-project/remarshal/commit/ee9a5b5d5ed82d90223a1d5fc74a4d546a034830 | 18:04:40 |
| emily | looks like they endorse your plan | 18:04:45 |
| hexa | that is the outcome of https://github.com/remarshal-project/remarshal/issues/52 | 18:05:16 |
| emily | I would be inclined to just introduce pkgs.formats.yaml12 for the new version even | 18:06:22 |
| hexa | or that, yeah | 18:07:00 |
| 9 Nov 2024 |
| hexa | https://github.com/NixOS/nixpkgs/pull/354687 | 05:36:07 |
| 11 Nov 2024 |
|  Jesse joined the room. | 03:50:08 |
| 12 Nov 2024 |
|  pfhuh joined the room. | 05:55:18 |
|  nienormalnie joined the room. | 06:27:26 |
|  @azahi:azahi.cc changed their profile picture. | 18:51:18 |
| 13 Nov 2024 |
|  @jan:smittie.de joined the room. | 15:55:12 |
|  Inayet joined the room. | 22:16:48 |
| 14 Nov 2024 |
 vcunat | staging-next merged. I'm not aware of any blocker. | 07:38:07 |
| vcunat | Merge blocker at least. I expect that nixStatic and perhaps some other regressions are desirable to fix before releasing. | 07:39:20 |
 Tristan Ross | Oh fun, tomorrow is branch off | 07:41:21 |
| vcunat | I have Nov 14th for quite some time already 😉 | 07:42:07 |
| Tristan Ross | Yeah, I think it'll be time to pick the 25.05 codename now heh | 07:44:42 |
 Scrumplex | If Kubernetes can have Kuwubernetes, can we have something cute too? Like an Axolotl? | 07:48:31 |
 Ilan Joselevich (Kranzes) | We're on letter V | 07:49:31 |
| Scrumplex | In that case I'll have to wait for NixOS 27.05 Axolotl | 07:51:41 |
| vcunat | 24.11 Vicuna has been chosen already. | 07:52:18 |
