You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(101) |
Jun
(157) |
Jul
(89) |
Aug
(135) |
Sep
(17) |
Oct
(86) |
Nov
(410) |
Dec
(311) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(76) |
Feb
(100) |
Mar
(139) |
Apr
(138) |
May
(234) |
Jun
(178) |
Jul
(271) |
Aug
(286) |
Sep
(816) |
Oct
(50) |
Nov
(28) |
Dec
(137) |
2003 |
Jan
(62) |
Feb
(25) |
Mar
(97) |
Apr
(34) |
May
(35) |
Jun
(32) |
Jul
(32) |
Aug
(57) |
Sep
(67) |
Oct
(176) |
Nov
(36) |
Dec
(37) |
2004 |
Jan
(20) |
Feb
(93) |
Mar
(16) |
Apr
(36) |
May
(59) |
Jun
(48) |
Jul
(20) |
Aug
(154) |
Sep
(868) |
Oct
(41) |
Nov
(63) |
Dec
(60) |
2005 |
Jan
(59) |
Feb
(15) |
Mar
(16) |
Apr
(14) |
May
(19) |
Jun
(16) |
Jul
(25) |
Aug
(19) |
Sep
(7) |
Oct
(12) |
Nov
(18) |
Dec
(41) |
2006 |
Jan
(16) |
Feb
(65) |
Mar
(51) |
Apr
(75) |
May
(38) |
Jun
(25) |
Jul
(23) |
Aug
(16) |
Sep
(24) |
Oct
(3) |
Nov
(1) |
Dec
(10) |
2007 |
Jan
(4) |
Feb
(5) |
Mar
(7) |
Apr
(29) |
May
(38) |
Jun
(3) |
Jul
(1) |
Aug
(17) |
Sep
(1) |
Oct
|
Nov
(11) |
Dec
(16) |
2008 |
Jan
(11) |
Feb
(4) |
Mar
(7) |
Apr
(48) |
May
(17) |
Jun
(9) |
Jul
(6) |
Aug
(12) |
Sep
(5) |
Oct
(7) |
Nov
(4) |
Dec
(11) |
2009 |
Jan
(15) |
Feb
(28) |
Mar
(12) |
Apr
(44) |
May
(6) |
Jun
(16) |
Jul
(6) |
Aug
(37) |
Sep
(107) |
Oct
(24) |
Nov
(30) |
Dec
(22) |
2010 |
Jan
(8) |
Feb
(16) |
Mar
(11) |
Apr
(28) |
May
(9) |
Jun
(26) |
Jul
(7) |
Aug
(25) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
2011 |
Jan
(5) |
Feb
(6) |
Mar
(3) |
Apr
(2) |
May
(10) |
Jun
(44) |
Jul
(11) |
Aug
(8) |
Sep
(6) |
Oct
(42) |
Nov
(19) |
Dec
(5) |
2012 |
Jan
(23) |
Feb
(8) |
Mar
(9) |
Apr
(11) |
May
(2) |
Jun
(11) |
Jul
|
Aug
(18) |
Sep
(1) |
Oct
(15) |
Nov
(14) |
Dec
(8) |
2013 |
Jan
(5) |
Feb
(13) |
Mar
(2) |
Apr
(10) |
May
|
Jun
(6) |
Jul
(17) |
Aug
(2) |
Sep
(3) |
Oct
|
Nov
(11) |
Dec
|
2014 |
Jan
|
Feb
(1) |
Mar
(10) |
Apr
(12) |
May
(1) |
Jun
(9) |
Jul
(27) |
Aug
(5) |
Sep
(13) |
Oct
(9) |
Nov
(9) |
Dec
|
2015 |
Jan
(8) |
Feb
(5) |
Mar
(1) |
Apr
(10) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(2) |
Oct
(14) |
Nov
(1) |
Dec
(6) |
2016 |
Jan
(12) |
Feb
(12) |
Mar
(133) |
Apr
(7) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
(3) |
Nov
(5) |
Dec
|
2017 |
Jan
(2) |
Feb
|
Mar
(3) |
Apr
|
May
(1) |
Jun
(8) |
Jul
(2) |
Aug
(2) |
Sep
(8) |
Oct
(2) |
Nov
(8) |
Dec
(1) |
2018 |
Jan
(1) |
Feb
(2) |
Mar
(6) |
Apr
|
May
(1) |
Jun
(4) |
Jul
(1) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2019 |
Jan
(2) |
Feb
(2) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
(1) |
Dec
(2) |
2020 |
Jan
(5) |
Feb
|
Mar
(2) |
Apr
(6) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2021 |
Jan
(5) |
Feb
(2) |
Mar
(6) |
Apr
(1) |
May
(1) |
Jun
(3) |
Jul
|
Aug
(5) |
Sep
|
Oct
(5) |
Nov
(1) |
Dec
(4) |
2022 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
(1) |
Dec
(1) |
2023 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(2) |
2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: G. G <geo...@gm...> - 2024-06-24 11:44:47
|
From: Brent T. <tho...@gm...> - 2024-06-14 03:59:26
|
https://lists.sourceforge.net/lists/listinfo/yaml-core yam...@li... |
From: Conor L. <con...@gm...> - 2023-12-20 22:16:43
|
I've got a c application that receives a stream of yaml data in multiple chunks. Is libyaml suitable for parsing incomplete yaml data? i.e. being passed each of the chunks of data as they are received? and libyaml handling detecting that the data is incomplete and waiting for the next chunk to be received. Regards, Conor |
From: William R. <bil...@gm...> - 2023-12-13 17:05:00
|
I have been using the yaml_document_add methods to build a yaml_document_t and then emit it. Everything has been working fine for emitting maps and sequences. However, what if I just wanted my yaml output to be just a scalar? I've tried using yaml_document_add_scalar() but it just outputs "{}". Is there an api for adding something like "foo" to the yaml_document_t so the output is just "foo". To help debug this I added some printfs to libyaml and Python using the pylibyaml bindings where I get the output I expected (see below). It seems its using the event based stream API, is that the only way this is supported? Is my understanding of what valid yaml is incorrect (I just used yamllint.com to validate). Is this just a byproduct of the stream based emitters/parsers? #!/usr/bin/env python import pylibyaml import yaml import os s="foo" x = yaml.safe_dump(s) print(x) which prints: ./test.py BILL: yaml_emitter_initialize BILL: yaml_emitter_set_output BILL: yaml_stream_start_event_initialize BILL: yaml_event_delete BILL: yaml_document_start_event_initialize BILL: yaml_scalar_event_initialize BILL: yaml_check_utf8 BILL: yaml_check_utf8 BILL: yaml_event_delete BILL: yaml_event_delete BILL: yaml_document_end_event_initialize BILL: yaml_event_delete BILL: yaml_stream_end_event_initialize BILL: yaml_event_delete BILL: yaml_emitter_delete foo |
From: <ma...@vp...> - 2023-11-18 22:06:32
|
0export PROJECT_ID="my-test-project" gcloud projects get-iam-policy $PROJECT_ID test serwer [ID aplikacja -- (_¼=⁵⁸⅓Wiśniewski .___.*€/= W dniu 2023-11-17 14:51:49 użytkownik Volkswagen Polska <ko...@ma...> napisał: Ruszaj po supermocne okazje! Jeśli wiadomość nie wyświetliła się poprawnie, kliknij tutaj by przejść do oferty. Wiadomość wysłana przez Data Matters Global Limited, Office no 22, Alpha Centre, Providence, Mache, Seychelles. Wiadomość została wysłana na zlecenie Volkswagen Group Polska Sp. z o.o. ul. Krańcowa 44, 61-037 Poznań, Sąd Rejonowy Poznań - Nowe Miasto i Wilda w Poznaniu,VIII Wydział Gospodarczy Krajowego Rejestru Sądowego KRS nr 0000327143 INS Kapitał zakładowy 331009000,00 PLN NIP 782246353, REGON 301062169. Zgodnie z działalnością serwisu, dysponujesz prawem dostępu, zmiany, sprostowania i usuwania swoich informacji osobowych. Jeśli chcesz zrezygnować z możliwości otrzymywania wiadomości kliknij: tutaj. W przypadku pytań dotyczących prezentowanych produktów i usług, prosimy o zwracanie się bezpośrednio do reklamodawcy. Wszelkie informacje można uzyskać pisząc na adres: po...@da... |
From: mohamed E. <sco...@gm...> - 2023-06-17 15:40:20
|
thanks |
From: mohamed E. <sco...@gm...> - 2023-06-17 15:40:07
|
thanks |
From: mosa-awe <my...@gm...> - 2023-04-08 00:55:19
|
https://ttt6737739.com/ |
From: Melvin O. <mel...@gm...> - 2023-02-26 18:11:56
|
From: Saad H. <yas...@gm...> - 2022-12-27 03:45:18
|
saad hussien |
From: joylix <jo...@12...> - 2022-11-29 04:18:34
|
Folks, Are there any tools or methods to convert rdf into yaml format files? |
From: Saad H. <yas...@gm...> - 2022-10-20 20:28:08
|
saad hussien |
From: Saad H. <yas...@gm...> - 2022-10-09 21:24:17
|
saad hussien |
From: <ma...@vp...> - 2022-10-09 18:28:19
|
.. |
From: yuqieang c. <yuq...@gm...> - 2022-04-03 00:06:26
|
-- 发自移动版 Gmail |
From: Dan D. <you...@ic...> - 2022-02-28 23:14:45
|
Please help me get my photography bk that was stolen when they were hacking me. There’s nothing like it on the internet. It’s very different art work. Sent from my iPhone |
From: Shawn G. <sha...@gm...> - 2022-02-09 19:20:44
|
I'm the new maintainer for the R yaml package and it relies on libyaml as it's library. I'm trying to get up to speed and have a few questions. 1) Are there compile flag options that change behavior of the library? If so, how do I learn about them. 2) What's the status of moving toward yaml 1.2 support? It seems like it's almost there. -- Shawn Garbett 615.397.8737 |
From: Isha F. <ich...@gm...> - 2022-01-07 00:04:52
|
-- null |
From: Andrey S. <pub...@gm...> - 2021-12-21 08:07:06
|
Thank you for the answer. I will try to continue in Elements Cheers, Andrey On Mon, Dec 20, 2021 at 9:51 PM Ingy dot Net <in...@in...> wrote: > Hi Andrey! > > As a reminder, we don't use the mailing list for this or almost anything > anymore. > The YAML language design team <https://yaml.org/spec/1.2.2/ext/team/> is > very active these days and we have a host of modern ways to engage. > > The short answer to your query is that in this case libyaml is right and > pyyaml is wrong. > Apologies for the libyaml tests not running out of the box. > That's on me, and I'll try to find some time to fix this at some point. > > https://play.yaml.io/main/parser?input=ImJhciIJ shows the results of 14 > YAML parsers, and PyYAML, Ruamel (fork of PyYAML) and SnakeYAML get this > one wrong. > The New Reference Parser <https://github.com/yaml/yaml-reference-parser/> > there is literally *generated* from the spec productions and therefore is > almost always correct in its interpretation. > That might be a useful resource for you. > > The productions involved in the (recently published > <https://yaml.com/blog/2021-10/new-yaml-spec/>) 1.2.2 spec > <https://yaml.org/spec/1.2.2/> are: > > - https://yaml.org/spec/1.2.2/#rule-c-ns-flow-map-json-key-entry > - https://yaml.org/spec/1.2.2/#rule-c-flow-json-node > - https://yaml.org/spec/1.2.2/#rule-c-double-quoted > - https://yaml.org/spec/1.2.2/#rule-s-separate > - https://yaml.org/spec/1.2.2/#rule-s-separate-in-line > - https://yaml.org/spec/1.2.2/#rule-s-white > - Which is spaces and tabs > > Put another way, non-indentation whitespace is usually tabs and spaces. > Note: I'm not personally a fan of allowing tabs anywhere (except in > literal scalar content), but that's where the 1.2 productions stand. > > I assume you are aware of the YAML test suite > <https://github.com/yaml/yaml-test-suite>. > Our testing of compliant frameworks is shown in the YAML Test Matrix > <https://matrix.yaml.info/>. > SnakeYAML <https://bitbucket.org/snakeyaml/snakeyaml/src/master/> is > failing quite a bit, but then again so are libyaml and PyYAML. > Unfortunately we don't yet have support for SnakeYAML Engine > <https://bitbucket.org/snakeyaml/snakeyaml-engine/src/master/> yet but we > just need someone to write a port of the tester > <https://github.com/yaml/yaml-runtimes/blob/3411ed2868d4bc5b8c9c5f421565d2c887892329/docker/java/utils/java/src/test/java/org/yaml/editor/Snake2EventsTest.java> to > have it included in the results. > Also, speaking of libyaml, I should point out the new C library for yaml > called libfyaml <https://github.com/pantoniou/libfyaml> which is quite an > amazing work. > > Regarding the testing of libyaml (and everything else), running 'make > clean run-tests export' in the YAML test suite directory creates an > export.tsv file which we copy/paste into this Google Sheet > <https://docs.google.com/spreadsheets/d/e/2PACX-1vSlIvGsUqrCvf4s9PhVJeAyvvlx0rOfZFgox4ZexwCYpPH0gdkQN36o0AJaDageHbLp-FgY538FLO5c/pubhtml?gid=0&single=true> (with > results totals) when the suite is updated. > So that's an alternate way of testing libyaml... > > We have a rather new community platform > <https://matrix.to/#/%23chat:yaml.io> for engaging directly with the core > team about YAML development or anything else YAML related. > If you haven't used element/matrix, I'd describe it as completely open and > secure Slack. > It works great, has great desktop and phone clients but also works just as > good in a browser, and is trivial to join. > > I'll also reply directly to your PyYAML issue > <https://github.com/yaml/pyyaml/issues/594>. :) > > Almost all this info is on the plain old https://yaml.org/ site which we > are actively keeping up to date. > > But personally, Andrey, I really hope you join the new chat. > We really want SnakeYAML to be as good as possible, and have been hoping > to engage with you! > > BTW, no foul in posting here. > It gave me a great excuse to promote some of the recent YAML work. > I hope you and other readers find it useful. > > Thanks and happy end of 2021! > > — Ingy > > On Mon, Dec 20, 2021 at 2:33 AM Andrey Somov <pub...@gm...> > wrote: > >> Hi all, >> I wanted to have a look at LibYAML to understand the reason for >> https://github.com/yaml/pyyaml/issues/594 >> >> Unfortunately the tests fail in master. >> Can you please help me to make the tests run ? >> >> tests/run-all-tests.sh >> ... >> make[2]: Entering directory >> '/home/ooosssmmm/rev-projects/yaml/libyaml/tests' >> PASS: test-version >> PASS: test-reader >> >> ============================================================================ >> Testsuite summary for yaml 0.2.5 >> >> ============================================================================ >> # TOTAL: 2 >> # PASS: 2 >> # SKIP: 0 >> # XFAIL: 0 >> # FAIL: 0 >> # XPASS: 0 >> # ERROR: 0 >> >> ============================================================================ >> make[2]: Leaving directory >> '/home/ooosssmmm/rev-projects/yaml/libyaml/tests' >> make[1]: Leaving directory >> '/home/ooosssmmm/rev-projects/yaml/libyaml/tests' >> git branch --track run-test-suite origin/run-test-suite >> fatal: A branch named 'run-test-suite' already exists. >> make: [Makefile:888: tests/run-test-suite] Error 128 (ignored) >> git worktree prune >> git worktree add tests/run-test-suite run-test-suite >> Preparing worktree (checking out 'run-test-suite') >> HEAD is now at 7b73fcf Move testing code into run-test-suite-code branch >> make -C tests/run-test-suite test >> make[1]: Entering directory >> '/home/ooosssmmm/rev-projects/yaml/libyaml/tests/run-test-suite' >> git clone https://github.com/yaml/yaml-test-suite data --branch=data >> Cloning into 'data'... >> remote: Enumerating objects: 16712, done. >> remote: Counting objects: 100% (2667/2667), done. >> remote: Compressing objects: 100% (1313/1313), done. >> remote: Total 16712 (delta 1663), reused 2067 (delta 1160), pack-reused >> 14045 >> Receiving objects: 100% (16712/16712), 4.84 MiB | 2.24 MiB/s, done. >> Resolving deltas: 100% (10668/10668), done. >> (cd data && git reset --hard daf799e56372aa93c324d111c73b47a431d7e03b) >> fatal: Could not parse object 'daf799e56372aa93c324d111c73b47a431d7e03b'. >> make[1]: *** [Makefile:25: data] Error 128 >> make[1]: Leaving directory >> '/home/ooosssmmm/rev-projects/yaml/libyaml/tests/run-test-suite' >> make: *** [Makefile:882: test-suite] Error 2 >> _______________________________________________ >> Yaml-core mailing list >> Yam...@li... >> https://lists.sourceforge.net/lists/listinfo/yaml-core >> > |
From: Ingy d. N. <in...@in...> - 2021-12-20 18:17:05
|
Hi Andrey! As a reminder, we don't use the mailing list for this or almost anything anymore. The YAML language design team <https://yaml.org/spec/1.2.2/ext/team/> is very active these days and we have a host of modern ways to engage. The short answer to your query is that in this case libyaml is right and pyyaml is wrong. Apologies for the libyaml tests not running out of the box. That's on me, and I'll try to find some time to fix this at some point. https://play.yaml.io/main/parser?input=ImJhciIJ shows the results of 14 YAML parsers, and PyYAML, Ruamel (fork of PyYAML) and SnakeYAML get this one wrong. The New Reference Parser <https://github.com/yaml/yaml-reference-parser/> there is literally *generated* from the spec productions and therefore is almost always correct in its interpretation. That might be a useful resource for you. The productions involved in the (recently published <https://yaml.com/blog/2021-10/new-yaml-spec/>) 1.2.2 spec <https://yaml.org/spec/1.2.2/> are: - https://yaml.org/spec/1.2.2/#rule-c-ns-flow-map-json-key-entry - https://yaml.org/spec/1.2.2/#rule-c-flow-json-node - https://yaml.org/spec/1.2.2/#rule-c-double-quoted - https://yaml.org/spec/1.2.2/#rule-s-separate - https://yaml.org/spec/1.2.2/#rule-s-separate-in-line - https://yaml.org/spec/1.2.2/#rule-s-white - Which is spaces and tabs Put another way, non-indentation whitespace is usually tabs and spaces. Note: I'm not personally a fan of allowing tabs anywhere (except in literal scalar content), but that's where the 1.2 productions stand. I assume you are aware of the YAML test suite <https://github.com/yaml/yaml-test-suite>. Our testing of compliant frameworks is shown in the YAML Test Matrix <https://matrix.yaml.info/>. SnakeYAML <https://bitbucket.org/snakeyaml/snakeyaml/src/master/> is failing quite a bit, but then again so are libyaml and PyYAML. Unfortunately we don't yet have support for SnakeYAML Engine <https://bitbucket.org/snakeyaml/snakeyaml-engine/src/master/> yet but we just need someone to write a port of the tester <https://github.com/yaml/yaml-runtimes/blob/3411ed2868d4bc5b8c9c5f421565d2c887892329/docker/java/utils/java/src/test/java/org/yaml/editor/Snake2EventsTest.java> to have it included in the results. Also, speaking of libyaml, I should point out the new C library for yaml called libfyaml <https://github.com/pantoniou/libfyaml> which is quite an amazing work. Regarding the testing of libyaml (and everything else), running 'make clean run-tests export' in the YAML test suite directory creates an export.tsv file which we copy/paste into this Google Sheet <https://docs.google.com/spreadsheets/d/e/2PACX-1vSlIvGsUqrCvf4s9PhVJeAyvvlx0rOfZFgox4ZexwCYpPH0gdkQN36o0AJaDageHbLp-FgY538FLO5c/pubhtml?gid=0&single=true> (with results totals) when the suite is updated. So that's an alternate way of testing libyaml... We have a rather new community platform <https://matrix.to/#/#chat:yaml.io> for engaging directly with the core team about YAML development or anything else YAML related. If you haven't used element/matrix, I'd describe it as completely open and secure Slack. It works great, has great desktop and phone clients but also works just as good in a browser, and is trivial to join. I'll also reply directly to your PyYAML issue <https://github.com/yaml/pyyaml/issues/594>. :) Almost all this info is on the plain old https://yaml.org/ site which we are actively keeping up to date. But personally, Andrey, I really hope you join the new chat. We really want SnakeYAML to be as good as possible, and have been hoping to engage with you! BTW, no foul in posting here. It gave me a great excuse to promote some of the recent YAML work. I hope you and other readers find it useful. Thanks and happy end of 2021! — Ingy On Mon, Dec 20, 2021 at 2:33 AM Andrey Somov <pub...@gm...> wrote: > Hi all, > I wanted to have a look at LibYAML to understand the reason for > https://github.com/yaml/pyyaml/issues/594 > > Unfortunately the tests fail in master. > Can you please help me to make the tests run ? > > tests/run-all-tests.sh > ... > make[2]: Entering directory > '/home/ooosssmmm/rev-projects/yaml/libyaml/tests' > PASS: test-version > PASS: test-reader > > ============================================================================ > Testsuite summary for yaml 0.2.5 > > ============================================================================ > # TOTAL: 2 > # PASS: 2 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 0 > # XPASS: 0 > # ERROR: 0 > > ============================================================================ > make[2]: Leaving directory > '/home/ooosssmmm/rev-projects/yaml/libyaml/tests' > make[1]: Leaving directory > '/home/ooosssmmm/rev-projects/yaml/libyaml/tests' > git branch --track run-test-suite origin/run-test-suite > fatal: A branch named 'run-test-suite' already exists. > make: [Makefile:888: tests/run-test-suite] Error 128 (ignored) > git worktree prune > git worktree add tests/run-test-suite run-test-suite > Preparing worktree (checking out 'run-test-suite') > HEAD is now at 7b73fcf Move testing code into run-test-suite-code branch > make -C tests/run-test-suite test > make[1]: Entering directory > '/home/ooosssmmm/rev-projects/yaml/libyaml/tests/run-test-suite' > git clone https://github.com/yaml/yaml-test-suite data --branch=data > Cloning into 'data'... > remote: Enumerating objects: 16712, done. > remote: Counting objects: 100% (2667/2667), done. > remote: Compressing objects: 100% (1313/1313), done. > remote: Total 16712 (delta 1663), reused 2067 (delta 1160), pack-reused > 14045 > Receiving objects: 100% (16712/16712), 4.84 MiB | 2.24 MiB/s, done. > Resolving deltas: 100% (10668/10668), done. > (cd data && git reset --hard daf799e56372aa93c324d111c73b47a431d7e03b) > fatal: Could not parse object 'daf799e56372aa93c324d111c73b47a431d7e03b'. > make[1]: *** [Makefile:25: data] Error 128 > make[1]: Leaving directory > '/home/ooosssmmm/rev-projects/yaml/libyaml/tests/run-test-suite' > make: *** [Makefile:882: test-suite] Error 2 > _______________________________________________ > Yaml-core mailing list > Yam...@li... > https://lists.sourceforge.net/lists/listinfo/yaml-core > |
From: Andrey S. <pub...@gm...> - 2021-12-20 07:33:10
|
Hi all, I wanted to have a look at LibYAML to understand the reason for https://github.com/yaml/pyyaml/issues/594 Unfortunately the tests fail in master. Can you please help me to make the tests run ? tests/run-all-tests.sh ... make[2]: Entering directory '/home/ooosssmmm/rev-projects/yaml/libyaml/tests' PASS: test-version PASS: test-reader ============================================================================ Testsuite summary for yaml 0.2.5 ============================================================================ # TOTAL: 2 # PASS: 2 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0 ============================================================================ make[2]: Leaving directory '/home/ooosssmmm/rev-projects/yaml/libyaml/tests' make[1]: Leaving directory '/home/ooosssmmm/rev-projects/yaml/libyaml/tests' git branch --track run-test-suite origin/run-test-suite fatal: A branch named 'run-test-suite' already exists. make: [Makefile:888: tests/run-test-suite] Error 128 (ignored) git worktree prune git worktree add tests/run-test-suite run-test-suite Preparing worktree (checking out 'run-test-suite') HEAD is now at 7b73fcf Move testing code into run-test-suite-code branch make -C tests/run-test-suite test make[1]: Entering directory '/home/ooosssmmm/rev-projects/yaml/libyaml/tests/run-test-suite' git clone https://github.com/yaml/yaml-test-suite data --branch=data Cloning into 'data'... remote: Enumerating objects: 16712, done. remote: Counting objects: 100% (2667/2667), done. remote: Compressing objects: 100% (1313/1313), done. remote: Total 16712 (delta 1663), reused 2067 (delta 1160), pack-reused 14045 Receiving objects: 100% (16712/16712), 4.84 MiB | 2.24 MiB/s, done. Resolving deltas: 100% (10668/10668), done. (cd data && git reset --hard daf799e56372aa93c324d111c73b47a431d7e03b) fatal: Could not parse object 'daf799e56372aa93c324d111c73b47a431d7e03b'. make[1]: *** [Makefile:25: data] Error 128 make[1]: Leaving directory '/home/ooosssmmm/rev-projects/yaml/libyaml/tests/run-test-suite' make: *** [Makefile:882: test-suite] Error 2 |
From: Reading O. <qa...@gm...> - 2021-12-19 18:03:55
|
From: Isha F. <sh...@e-...> - 2021-11-15 14:32:27
|
Any.do Isha Fazil shared a list with you: = Work = ACCEPT <https://sm-prod3.any.do/api/v1/action_from_email/accept/CQ69OrCKSiiGy596pvrZbA%3D%3D/yaml-core%40lists.sourceforge.net?token=4ab65301fbac1861669ac14301f1b22d&tag=category-shared-to-non-anydo> Isha Fazil is using Any.do to keep life under control and get more done Any.do Inc. © 2021 All rights Reserved | Don't want these emails? Unsubscribe <http://mandrillapp.com/track/unsub.php?u=30174109&id=569d8f4b2f8b4de78ae6437e5fcbb8e4.6YUp8npv1J%2B1Zj9vlvIYpM4CacQ%3D&r=http%3A%2F%2Fwww.any.do%2Funsubscribe%3Fmd_email%3Dy%252A%252A%252A%252A%2540l%252A%252A%252A%252A.%252A%252A%252A> |
From: Ingy d. N. <in...@in...> - 2021-10-13 19:43:30
|
===================== Announcing PyYAML-6.0 ===================== A new release of PyYAML is now available: https://github.com/yaml/pyyaml/releases/tag/6.0 The previously-deprecated default loader selection in `yaml.load()` has been removed; `Loader` is now a required argument. Support for Python 2.7 and 3.5 has been dropped, and support for Python 3.10 added. It now includes libyaml 0.2.5 extension wheels for MacOS M1 (Apple Silicon/arm64), Linux s390x and Linux aarch64. Numerous other bugfixes and code cleanups are included in this release. Changes ======= * https://github.com/yaml/pyyaml/pull/327 -- Change README format to Markdown * https://github.com/yaml/pyyaml/pull/483 -- Add a test for YAML 1.1 types * https://github.com/yaml/pyyaml/pull/497 -- fix float resolver to ignore `.` and `._` * https://github.com/yaml/pyyaml/pull/550 -- drop Python 2.7 * https://github.com/yaml/pyyaml/pull/553 -- Fix spelling of “hexadecimal” * https://github.com/yaml/pyyaml/pull/556 -- fix representation of Enum subclasses * https://github.com/yaml/pyyaml/pull/557 -- fix libyaml extension compiler warnings * https://github.com/yaml/pyyaml/pull/560 -- fix ResourceWarning on leaked file descriptors * https://github.com/yaml/pyyaml/pull/561 -- always require `Loader` arg to `yaml.load()` * https://github.com/yaml/pyyaml/pull/564 -- remove remaining direct distutils usage Resources ========= PyYAML Matrix: https://matrix.to/#/#pyyaml:yaml.io PyYAML IRC Channel: #pyyaml on irc.libera.chat PyYAML homepage: https://github.com/yaml/pyyaml PyYAML documentation: http://pyyaml.org/wiki/PyYAMLDocumentation Source and binary installers: https://pypi.org/project/PyYAML/ GitHub repository: https://github.com/yaml/pyyaml/ Bug tracking: https://github.com/yaml/pyyaml/issues YAML homepage: http://yaml.org/ YAML-core mailing list: http://lists.sourceforge.net/lists/listinfo/yaml-core About PyYAML ============ YAML is a data serialization format designed for human readability and interaction with scripting languages. PyYAML is a YAML parser and emitter for Python. PyYAML features a complete YAML 1.1 parser, Unicode support, pickle support, capable extension API, and sensible error messages. PyYAML supports standard YAML tags and provides Python-specific tags that allow to represent an arbitrary Python object. PyYAML is applicable for a broad range of tasks from complex configuration files to object serialization and persistence. Example ======= ``` >>> import yaml >>> yaml.full_load(""" ... name: PyYAML ... description: YAML parser and emitter for Python ... homepage: https://github.com/yaml/pyyaml ... keywords: [YAML, serialization, configuration, persistence, pickle] ... """) {'keywords': ['YAML', 'serialization', 'configuration', 'persistence', 'pickle'], 'homepage': 'https://github.com/yaml/pyyaml', 'description': 'YAML parser and emitter for Python', 'name': 'PyYAML'} >>> print(yaml.dump(_)) name: PyYAML homepage: https://github.com/yaml/pyyaml description: YAML parser and emitter for Python keywords: [YAML, serialization, configuration, persistence, pickle] ``` Maintainers =========== The following people are currently responsible for maintaining PyYAML: * Ingy döt Net * Matt Davis and many thanks to all who have contributed! See: https://github.com/yaml/pyyaml/pulls Copyright ========= Copyright (c) 2017-2021 Ingy döt Net <in...@in...> Copyright (c) 2006-2016 Kirill Simonov <xi...@re...> The PyYAML module was written by Kirill Simonov <xi...@re...>. It is currently maintained by the YAML and Python communities. PyYAML is released under the MIT license. See the file LICENSE for more details. |
From: Ingy d. N. <in...@in...> - 2021-10-04 22:28:12
|
======================= Announcing PyYAML-6.0b1 ======================= A new beta release of PyYAML is now available: https://github.com/yaml/pyyaml/releases/tag/6.0b1 The previously-deprecated default loader selection in `yaml.load()` has been removed; `Loader` is now a required argument. Support for Python 2.7 and 3.5 has been dropped, and support for Python 3.10 added. It now includes libyaml 0.2.5 extension wheels for MacOS M1 (Apple Silicon/arm64), Linux s390x and Linux aarch64. Numerous other bugfixes and code cleanups are included in this release. Changes ======= * https://github.com/yaml/pyyaml/pull/327 -- Change README format to Markdown * https://github.com/yaml/pyyaml/pull/483 -- Add a test for YAML 1.1 types * https://github.com/yaml/pyyaml/pull/497 -- fix float resolver to ignore `.` and `._` * https://github.com/yaml/pyyaml/pull/550 -- drop Python 2.7 * https://github.com/yaml/pyyaml/pull/553 -- Fix spelling of “hexadecimal” * https://github.com/yaml/pyyaml/pull/556 -- fix representation of Enum subclasses * https://github.com/yaml/pyyaml/pull/557 -- fix libyaml extension compiler warnings * https://github.com/yaml/pyyaml/pull/560 -- fix ResourceWarning on leaked file descriptors * https://github.com/yaml/pyyaml/pull/561 -- always require `Loader` arg to `yaml.load()` * https://github.com/yaml/pyyaml/pull/564 -- remove remaining direct distutils usage Resources ========= PyYAML Matrix: https://matrix.to/#/#pyyaml:yaml.io PyYAML IRC Channel: #pyyaml on irc.libera.chat PyYAML homepage: https://github.com/yaml/pyyaml PyYAML documentation: http://pyyaml.org/wiki/PyYAMLDocumentation Source and binary installers: https://pypi.org/project/PyYAML/ GitHub repository: https://github.com/yaml/pyyaml/ Bug tracking: https://github.com/yaml/pyyaml/issues YAML homepage: http://yaml.org/ YAML-core mailing list: http://lists.sourceforge.net/lists/listinfo/yaml-core About PyYAML ============ YAML is a data serialization format designed for human readability and interaction with scripting languages. PyYAML is a YAML parser and emitter for Python. PyYAML features a complete YAML 1.1 parser, Unicode support, pickle support, capable extension API, and sensible error messages. PyYAML supports standard YAML tags and provides Python-specific tags that allow to represent an arbitrary Python object. PyYAML is applicable for a broad range of tasks from complex configuration files to object serialization and persistence. Example ======= ``` >>> import yaml >>> yaml.full_load(""" ... name: PyYAML ... description: YAML parser and emitter for Python ... homepage: https://github.com/yaml/pyyaml ... keywords: [YAML, serialization, configuration, persistence, pickle] ... """) {'keywords': ['YAML', 'serialization', 'configuration', 'persistence', 'pickle'], 'homepage': 'https://github.com/yaml/pyyaml', 'description': 'YAML parser and emitter for Python', 'name': 'PyYAML'} >>> print(yaml.dump(_)) name: PyYAML homepage: https://github.com/yaml/pyyaml description: YAML parser and emitter for Python keywords: [YAML, serialization, configuration, persistence, pickle] ``` Maintainers =========== The following people are currently responsible for maintaining PyYAML: * Ingy döt Net * Matt Davis and many thanks to all who have contributed! See: https://github.com/yaml/pyyaml/pulls Copyright ========= Copyright (c) 2017-2021 Ingy döt Net <in...@in...> Copyright (c) 2006-2016 Kirill Simonov <xi...@re...> The PyYAML module was written by Kirill Simonov <xi...@re...>. It is currently maintained by the YAML and Python communities. PyYAML is released under the MIT license. See the file LICENSE for more details. |