head	1.54;
access;
symbols
	pkgsrc-2026Q1:1.54.0.2
	pkgsrc-2026Q1-base:1.54
	pkgsrc-2025Q4:1.52.0.2
	pkgsrc-2025Q4-base:1.52
	pkgsrc-2025Q3:1.51.0.2
	pkgsrc-2025Q3-base:1.51
	pkgsrc-2025Q2:1.50.0.2
	pkgsrc-2025Q2-base:1.50
	pkgsrc-2025Q1:1.42.0.2
	pkgsrc-2025Q1-base:1.42
	pkgsrc-2024Q4:1.38.0.2
	pkgsrc-2024Q4-base:1.38
	pkgsrc-2024Q3:1.37.0.6
	pkgsrc-2024Q3-base:1.37
	pkgsrc-2024Q2:1.37.0.4
	pkgsrc-2024Q2-base:1.37
	pkgsrc-2024Q1:1.37.0.2
	pkgsrc-2024Q1-base:1.37
	pkgsrc-2023Q4:1.36.0.2
	pkgsrc-2023Q4-base:1.36
	pkgsrc-2023Q3:1.30.0.4
	pkgsrc-2023Q3-base:1.30
	pkgsrc-2023Q2:1.30.0.2
	pkgsrc-2023Q2-base:1.30
	pkgsrc-2023Q1:1.24.0.10
	pkgsrc-2023Q1-base:1.24
	pkgsrc-2022Q4:1.24.0.8
	pkgsrc-2022Q4-base:1.24
	pkgsrc-2022Q3:1.24.0.6
	pkgsrc-2022Q3-base:1.24
	pkgsrc-2022Q2:1.24.0.4
	pkgsrc-2022Q2-base:1.24
	pkgsrc-2022Q1:1.24.0.2
	pkgsrc-2022Q1-base:1.24
	pkgsrc-2021Q4:1.21.0.2
	pkgsrc-2021Q4-base:1.21
	pkgsrc-2021Q3:1.19.0.2
	pkgsrc-2021Q3-base:1.19
	pkgsrc-2021Q2:1.16.0.4
	pkgsrc-2021Q2-base:1.16
	pkgsrc-2021Q1:1.16.0.2
	pkgsrc-2021Q1-base:1.16
	pkgsrc-2020Q4:1.15.0.4
	pkgsrc-2020Q4-base:1.15
	pkgsrc-2020Q3:1.15.0.2
	pkgsrc-2020Q3-base:1.15
	pkgsrc-2020Q2:1.14.0.4
	pkgsrc-2020Q2-base:1.14
	pkgsrc-2020Q1:1.14.0.2
	pkgsrc-2020Q1-base:1.14
	pkgsrc-2019Q4:1.13.0.4
	pkgsrc-2019Q4-base:1.13
	pkgsrc-2019Q3:1.12.0.2
	pkgsrc-2019Q3-base:1.12
	pkgsrc-2019Q2:1.10.0.2
	pkgsrc-2019Q2-base:1.10
	pkgsrc-2019Q1:1.9.0.4
	pkgsrc-2019Q1-base:1.9
	pkgsrc-2018Q4:1.9.0.2
	pkgsrc-2018Q4-base:1.9
	pkgsrc-2018Q3:1.8.0.2
	pkgsrc-2018Q3-base:1.8
	pkgsrc-2018Q2:1.5.0.6
	pkgsrc-2018Q2-base:1.5
	pkgsrc-2018Q1:1.5.0.4
	pkgsrc-2018Q1-base:1.5
	pkgsrc-2017Q4:1.5.0.2
	pkgsrc-2017Q4-base:1.5
	pkgsrc-2017Q3:1.3.0.6
	pkgsrc-2017Q3-base:1.3
	pkgsrc-2017Q2:1.3.0.2
	pkgsrc-2017Q2-base:1.3
	pkgsrc-2017Q1:1.1.0.8
	pkgsrc-2017Q1-base:1.1
	pkgsrc-2016Q4:1.1.0.6
	pkgsrc-2016Q4-base:1.1
	pkgsrc-2016Q3:1.1.0.4
	pkgsrc-2016Q3-base:1.1
	pkgsrc-2016Q2:1.1.0.2
	pkgsrc-2016Q2-base:1.1;
locks; strict;
comment	@# @;


1.54
date	2026.01.04.14.45.30;	author adam;	state Exp;
branches;
next	1.53;
commitid	AFUqiaeOXBETk5pG;

1.53
date	2025.12.21.16.34.13;	author wiz;	state Exp;
branches;
next	1.52;
commitid	v0QVd4bgz3idoinG;

1.52
date	2025.10.30.13.18.32;	author wiz;	state Exp;
branches;
next	1.51;
commitid	yM3jPxrwqtGFYAgG;

1.51
date	2025.08.20.09.50.28;	author adam;	state Exp;
branches;
next	1.50;
commitid	6J0okWrrkn3M6s7G;

1.50
date	2025.06.10.16.36.16;	author adam;	state Exp;
branches;
next	1.49;
commitid	HMgWfeoDtkd7DmYF;

1.49
date	2025.06.08.18.12.21;	author adam;	state Exp;
branches;
next	1.48;
commitid	R5kOX38YGJjpe7YF;

1.48
date	2025.06.01.05.48.16;	author adam;	state Exp;
branches;
next	1.47;
commitid	6S8KQ0Kmrc54l9XF;

1.47
date	2025.05.26.05.11.37;	author adam;	state Exp;
branches;
next	1.46;
commitid	z7a6b5lkmZirknWF;

1.46
date	2025.04.12.20.13.34;	author adam;	state Exp;
branches;
next	1.45;
commitid	7MxlUMEdszFFJNQF;

1.45
date	2025.04.07.23.44.11;	author gdt;	state Exp;
branches;
next	1.44;
commitid	cflrHf4TDDUT3bQF;

1.44
date	2025.04.07.23.04.28;	author gdt;	state Exp;
branches;
next	1.43;
commitid	DKfvOH5zK6hhQaQF;

1.43
date	2025.04.07.17.54.08;	author gdt;	state Exp;
branches;
next	1.42;
commitid	FRb1S1T202tO79QF;

1.42
date	2025.01.12.10.25.43;	author wiz;	state Exp;
branches;
next	1.41;
commitid	cLtWptkdLIBmnbFF;

1.41
date	2025.01.05.21.21.48;	author adam;	state Exp;
branches;
next	1.40;
commitid	4osrga01l10helEF;

1.40
date	2025.01.02.13.57.33;	author adam;	state Exp;
branches;
next	1.39;
commitid	iKjaB3BdpwmTRUDF;

1.39
date	2024.12.31.16.13.54;	author adam;	state Exp;
branches;
next	1.38;
commitid	PIbTUyclVzDBGFDF;

1.38
date	2024.11.11.07.28.22;	author wiz;	state Exp;
branches;
next	1.37;
commitid	1fBDq3LwS98NncxF;

1.37
date	2024.02.07.09.00.10;	author adam;	state Exp;
branches;
next	1.36;
commitid	LrgH3w3Q4mSuPtXE;

1.36
date	2023.11.06.19.56.21;	author wiz;	state Exp;
branches;
next	1.35;
commitid	20QS8OE4Kvp2sALE;

1.35
date	2023.11.05.00.36.04;	author wiz;	state Exp;
branches;
next	1.34;
commitid	v7Nhu7xoVdGY3mLE;

1.34
date	2023.10.21.14.33.20;	author adam;	state Exp;
branches;
next	1.33;
commitid	epTZ02rkJnJ1bvJE;

1.33
date	2023.10.20.11.10.13;	author adam;	state Exp;
branches;
next	1.32;
commitid	sbh9yI38T6fh5mJE;

1.32
date	2023.10.04.11.39.18;	author adam;	state Exp;
branches;
next	1.31;
commitid	BMueVIeXDcsWKiHE;

1.31
date	2023.09.28.15.49.49;	author adam;	state Exp;
branches;
next	1.30;
commitid	nEZ6Ruyx9eM4lyGE;

1.30
date	2023.06.17.12.12.36;	author adam;	state Exp;
branches;
next	1.29;
commitid	SXC1gvahaQKPritE;

1.29
date	2023.06.06.10.46.01;	author wiz;	state Exp;
branches;
next	1.28;
commitid	hwjGmk4joOc9kSrE;

1.28
date	2023.05.30.07.58.41;	author wiz;	state Exp;
branches;
next	1.27;
commitid	wy4lyfhOunpHCXqE;

1.27
date	2023.05.10.05.19.29;	author adam;	state Exp;
branches;
next	1.26;
commitid	3PDHgFOVIXgNnnoE;

1.26
date	2023.05.07.08.40.15;	author wiz;	state Exp;
branches;
next	1.25;
commitid	snXFo4N4sb9NA0oE;

1.25
date	2023.05.04.17.23.59;	author adam;	state Exp;
branches;
next	1.24;
commitid	msor5jKoSEziAFnE;

1.24
date	2022.02.12.17.55.10;	author adam;	state Exp;
branches;
next	1.23;
commitid	Co8vvz6a4ayV5msD;

1.23
date	2022.01.04.20.53.37;	author wiz;	state Exp;
branches;
next	1.22;
commitid	CYyhdK9qtoffkmnD;

1.22
date	2022.01.04.12.35.59;	author adam;	state Exp;
branches;
next	1.21;
commitid	H6GmLrZUtozZzjnD;

1.21
date	2021.11.07.14.51.18;	author adam;	state Exp;
branches;
next	1.20;
commitid	mLcH5rb5TiP8cSfD;

1.20
date	2021.10.02.18.30.59;	author adam;	state Exp;
branches;
next	1.19;
commitid	nOf0HB4wgYWfzgbD;

1.19
date	2021.08.29.08.42.13;	author adam;	state Exp;
branches;
next	1.18;
commitid	R5uWg4Oj7Qu3pQ6D;

1.18
date	2021.08.26.07.30.05;	author adam;	state Exp;
branches;
next	1.17;
commitid	YQNiQZpebAcd6s6D;

1.17
date	2021.07.09.18.33.40;	author adam;	state Exp;
branches;
next	1.16;
commitid	c2YYHEeksQebjl0D;

1.16
date	2021.03.05.13.45.28;	author adam;	state Exp;
branches;
next	1.15;
commitid	Ok3UnDTC3rDJL7KC;

1.15
date	2020.09.05.07.06.43;	author wiz;	state Exp;
branches;
next	1.14;
commitid	GQ2puFmc2JrKnPmC;

1.14
date	2020.02.19.09.41.50;	author adam;	state Exp;
branches;
next	1.13;
commitid	e3jCTFOND23mDgXB;

1.13
date	2019.12.17.10.11.28;	author leot;	state Exp;
branches;
next	1.12;
commitid	OrKmTF7Uz6YKQ2PB;

1.12
date	2019.08.23.12.39.24;	author gdt;	state Exp;
branches;
next	1.11;
commitid	Kb4snImT8C8gp9AB;

1.11
date	2019.08.13.22.50.51;	author gdt;	state Exp;
branches;
next	1.10;
commitid	QRdvJ3eIQftk6VyB;

1.10
date	2019.05.07.09.29.38;	author adam;	state Exp;
branches;
next	1.9;
commitid	jSBoI0gVzRzFNfmB;

1.9
date	2018.10.14.16.26.51;	author adam;	state Exp;
branches;
next	1.8;
commitid	qUYw5F4rgHVFHWVA;

1.8
date	2018.08.14.14.54.26;	author adam;	state Exp;
branches;
next	1.7;
commitid	NfIuRM4SKtawa6OA;

1.7
date	2018.07.13.08.06.39;	author adam;	state Exp;
branches;
next	1.6;
commitid	fA10pJcxooWAWWJA;

1.6
date	2018.07.03.12.27.03;	author adam;	state Exp;
branches;
next	1.5;
commitid	YCUg8WQxn8GmHGIA;

1.5
date	2017.12.14.13.21.02;	author adam;	state Exp;
branches;
next	1.4;
commitid	pLjvbzZTvR92tRiA;

1.4
date	2017.10.28.08.51.25;	author adam;	state Exp;
branches;
next	1.3;
commitid	daabnmMGUDiauNcA;

1.3
date	2017.04.23.15.52.33;	author leot;	state Exp;
branches;
next	1.2;
commitid	zkDi1GnwkGEpQFOz;

1.2
date	2017.04.14.13.05.06;	author leot;	state Exp;
branches;
next	1.1;
commitid	C6opYplenFxRdvNz;

1.1
date	2016.05.16.13.52.54;	author nils;	state Exp;
branches;
next	;
commitid	jkNF9xiP5vdDbI6z;


desc
@@


1.54
log
@py-ruamel-yaml: updated to 0.19.1

0.19.0
- removed dependency on `ruamel.yaml.clibz`

0.19.0
- changed dependency on `ruamel.yaml.clib` to `ruamel.yaml.clibz`
  which includes support for free-threading (revisited after a bug
  report by [Ahmed Moustafa](https://sourceforge.net/u/aemous/profile/) and
  some insistance by [Nathan Goldbaum](https://sourceforge.net/u/ngoldbaum/profile/)
- added `.max_depth` to `YAML()` instance. If set to a (positive) number
  this limits the recursion, so loading does throw a `MaxDepthExceededError`.
  Based on comments by Benjamin Oberdorfer via email. This also triggered the
  new documenation section on processing unchecked input.
@
text
@# $NetBSD: Makefile,v 1.53 2025/12/21 16:34:13 wiz Exp $

DISTNAME=	ruamel_yaml-0.19.1
PKGNAME=	${PYPKGPREFIX}-${DISTNAME:S/_/-/1}
CATEGORIES=	devel python
MASTER_SITES=	${MASTER_SITE_PYPI:=r/ruamel.yaml/}

MAINTAINER=	pkgsrc-users@@NetBSD.org
HOMEPAGE=	https://yaml.dev/doc/ruamel.yaml/
COMMENT=	YAML parser/emitter
LICENSE=	mit

WRKSRC=		${WRKDIR}/${DISTNAME:S/_/./}

TOOL_DEPENDS+=	${PYPKGPREFIX}-setuptools>=78:../../devel/py-setuptools

USE_LANGUAGES=	# none

.include "../../lang/python/wheel.mk"
.include "../../mk/bsd.pkg.mk"
@


1.53
log
@py-ruamel-yaml: update to 0.18.17.

[0.18.17, 2025-12-17]:
- try to load C functions from `_ruamel_yaml_clibz` first.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.52 2025/10/30 13:18:32 wiz Exp $
d3 1
a3 1
DISTNAME=	ruamel_yaml-0.18.17
a13 1
#WHEEL_NAME=	${DISTNAME:S/./_/1}
a15 1
DEPENDS+=	${PYPKGPREFIX}-ruamel-yaml-clib>=0.2.7:../../devel/py-ruamel-yaml-clib
@


1.52
log
@py-ruamel-yaml: update to 0.18.16.

[0.18.16, 2025-10-22]:
- root level block style scalars that started with a directives-end marker or a
  document-end marker, are now indented 2 spaces.
- merged fix for accessing end_marks on Tokens provided by
  [Toknak](https://sourceforge.net/u/taknok/)
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.51 2025/08/20 09:50:28 adam Exp $
d3 2
a4 2
DISTNAME=	ruamel.yaml-0.18.16
PKGNAME=	${PYPKGPREFIX}-${DISTNAME:S/./-/1}
d13 2
a14 1
WHEEL_NAME=	${DISTNAME:S/./_/1}
@


1.51
log
@py-ruamel-yaml: updated to 0.18.15

0.18.15
- duplicate merge keys are never allowed (not even with .allow_duplicate_keys =
  True
- merge keys now keep there position if a key before the merge key gets deleted
  (previously a key after the merge key would move before it)
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.50 2025/06/10 16:36:16 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.18.15
d9 1
a9 1
HOMEPAGE=	https://yaml.readthedocs.io/
@


1.50
log
@py-ruamel-yaml: updated to 0.18.14

0.18.14
Unknown changes
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.49 2025/06/08 18:12:21 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.18.14
@


1.49
log
@py-ruamel-yaml: updated to 0.18.13

0.18.13

- Fix line wrapping on plain scalars not observing width correctly. Issue 529,
  reported by [Sebastien
  Vermeille](https://sourceforge.net/u/svermeille/profile/)
- Fix sha256 and length in RECORD files. Reported by
  [Evan](https://sourceforge.net/u/bempelise/profile/)
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.48 2025/06/01 05:48:16 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.18.13
@


1.48
log
@py-ruamel-yaml: updated to 0.18.12

0.18.12
- fix additional issue with extra space in double quoted string.
- fix duplicate key url, now pointing to yaml.dev.
- fix broken RECORD file, which was a problem for uv, not pip.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.47 2025/05/26 05:11:37 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.18.12
@


1.47
log
@py-ruamel-yaml: updated to 0.18.11

0.18.11
- function `load_yaml_guess_indent` now takes an option `yaml` argument so you can
  provide an already created/configured `YAML` instance
- Sequence item indicator with both comment/empty line before indicator **and** comment
  before sequence item, could not move comment and raise `NotImplementedError`. Reported
  by [Karsten Tessarzik](https://sourceforge.net/u/kars10/profile/).
- missing f for f-string (reported by π, via email)
- fixed issue with extra space in double quoted dump
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.46 2025/04/12 20:13:34 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.18.11
@


1.46
log
@Fix PLIST after py-setuptools update; bump depends and revision
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.45 2025/04/07 23:44:11 gdt Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.18.10
a4 1
PKGREVISION=	4
@


1.45
log
@devel/py-ruamel-yaml: Fix wheel name harder

setuptools has vendored wheel; vendored wheel and newer real wheel
disagree on handling of '.'.  Force real wheel, until we have new
setuptools with newer vendored wheel.

(Specific problem found by wiz@@; my prediction of more likely than not
to recur took only 31 minutes to come true.)
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.44 2025/04/07 23:04:28 gdt Exp $
d5 1
a5 1
PKGREVISION=	3
d14 3
a16 1
TOOL_DEPENDS+=	${PYPKGPREFIX}-setuptools-[0-9]*:../../devel/py-setuptools
a18 9
# The distfile uses '.' and the pkgsrc package uses '-'.  The
# wheelname uses '.' with old wheel code, such as is vendored in
# setuptools 75, and '_' with wheel >=0.45.1 (and likely setuptools
# 76).  Until then, force wheel so that the new code is used.
# (Afterwards, drop the TOOL_DEPENDS, keep WHEEL_NAME, and rewrite the
# comment.)
TOOL_DEPENDS+=	${PYPKGPREFIX}-wheel>=0.45.1:../../devel/py-wheel
WHEEL_NAME=	${DISTNAME:S/./_/1}

@


1.44
log
@devel/py-ruamel-yaml: Revert wheel name change

Despite having checked that all my installed packages were up to date
w.r.t. pkgsrc-current, now the wheel name is back to '.'.  My theory
is that if some other package (that isn't required) happens to be
installed, the behavior changes.

Upstream is warning about a future '.' to '_' transition.

For now, leave a comment about the wheel name mystery problem, to help
the next person debug, as I believe it's more likely than not that
the issue will recur.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.43 2025/04/07 17:54:08 gdt Exp $
d5 1
a5 1
PKGREVISION=	2
d17 8
a24 7
# The distfile uses '.' and the pkgsrc package uses '-'.

# The wheel intends to use '.', but with up-to-date pkgsrc (and
# perhaps more packages installed than strictly required), the wheel
# used '_'.  This is perhaps related to a pending renamed requested by
# PyPI.
#WHEEL_NAME=	${DISTNAME:S/./_/1}
@


1.43
log
@devel/py-ruamel-yaml: Adapt to new wheel name

Perhaps this is due to new setuptools, but the wheel name (in info
files) produced by the build has changed.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.42 2025/01/12 10:25:43 wiz Exp $
d5 1
a5 1
PKGREVISION=	1
d17 7
a23 2
# The distfile uses '.'; the pkgsrc package uses '-'; the wheel uses '_'.
WHEEL_NAME=	${DISTNAME:S/./_/1}
@


1.42
log
@py-ruamel-yaml: update to 0.18.10.

[0.18.10, 2025-01-06]:
- implemented changes to the setup.py for Python 3.14 as suggested by [Miro Hrončok](https://sourceforge.net/u/hroncok/profile/)
  in merge requests (MR not merged as those files are copied in from `develop` config)
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.41 2025/01/05 21:21:48 adam Exp $
d5 1
d17 3
@


1.41
log
@py-ruamel-yaml: updated to 0.18.9

0.18.9
- fix issue with roundtripping 0 in YAML 1.1
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.40 2025/01/02 13:57:33 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.18.9
@


1.40
log
@py-ruamel-yaml: updated to 0.18.8

0.18.8
- added warning to README.md that PyPI might block updates due to breaking changes
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.39 2024/12/31 16:13:54 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.18.8
@


1.39
log
@py-ruamel-yaml: updated to 0.18.7

0.18.7
- fixes for README
- fixes preservering anchor on scalar integer `0`
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.38 2024/11/11 07:28:22 wiz Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.18.7
@


1.38
log
@py-*: remove unused tool dependency

py-setuptools includes the py-wheel functionality nowadays
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.37 2024/02/07 09:00:10 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.18.6
a17 2
PYTHON_VERSIONS_INCOMPATIBLE=	27

@


1.37
log
@py-ruamel-yaml: updated to 0.18.6

0.18.6
- fixed an issue with dataclass loading when the fields were collections (bug found
  as a result of a question by [FibroMyAlgebra](https://stackoverflow.com/users/6855070/fibromyalgebra)
  on [StackOverflow](https://stackoverflow.com/a/77485786/1307905))
- fixed an issue loading dataclasses with `InitVar` fields when `from __future__ import
  annotations` was used to delay evaluation of typing.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.36 2023/11/06 19:56:21 wiz Exp $
a13 1
TOOL_DEPENDS+=	${PYPKGPREFIX}-wheel-[0-9]*:../../devel/py-wheel
@


1.36
log
@py-ruamel-yaml: update to 0.18.5.

[0.18.5, 2023-11-03]:
- there is some indication that dependent packages have been pinned to use specific
  (tested) and just install the latest even in Python versions that have end-of-life

[0.18.4, 2023-11-01]:
- YAML() instance has a `doc_infos` attribute which is a cumulative list of DocInfo
  instances (one for `load()`, one per document for `load_all()`). DocInfo instances
  contain version information (requested, directive) and tag directive information
- fix issue that the YAML instance tags attribute was not reset between documents,
  resulting in mixing of tag directives of multiple documents. Now only provides tag
  directive information on latest document after loading. This means tags for dumping
  must be set **again** after a document is loaded with the same instance. (because
  of this tags will be removed in a favour of a different mechanism in the future)
- fix issue with multiple document intermixing YAML 1.2 and YAML 1.1, the VersionedResolver
  now resets
- fix issue with disappearing comment when next token was Tag (still can't have both
  a comment before a tag and after a tag, before node)

[0.18.3, 2023-10-29]:
- fix issue with spurious newline on first item after comment + nested block sequence
- additional links in the metadata on PyPI (Reported, with pointers how to fix, by
  [Sorin](https://sourceforge.net/u/ssbarnea/profile/)).
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.35 2023/11/05 00:36:04 wiz Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.18.5
@


1.35
log
@py-ruamel-yaml: update to 0.18.2.

[0.18.2, 2023-10-24]:
- calling the deprecated functions now raises an `AttributeError` with the, somewhat
  more informative, orginal warning message. Instead of calling `sys.exit(1)`

[0.18.1, 2023-10-24]:
- calling the deprecated functions now always displays the warning message. (reported
  by [Trend Lloyd](https://sourceforge.net/u/lathiat2/profile/))

[0.18.0, 2023-10-23]:
- the **functions** `scan`, `parse`, `compose`, `load`, `emit`, `serialize`, `dump`
  and their variants (`_all`, `safe_`, `round_trip_`, etc) have been deprecated (the
  same named **methods** on `YAML()` instances are, of course, still there.
- |-
  `YAML(typ='unsafe')` now issues a `PendingDeprecationWarning`. This will become deprecated in the 0.18 series
  (probably before the end of 2023).
  You can use `YAML(typ='full')` to dump unregistered Python classes/functions.
  For loading you'll have to register your classes/functions
  if you want the old, unsafe, functionality. You can still load any tag, like `!!python/name:posix.system', **safely**
  with the (default) round-trip parser.
- fix for `bytes-like object is required not 'str' while dumping binary streams`.
  This was reported, analysed and a fix provided by [Vit Zikmund](https://sourceforge.net/u/tlwhitec/profile/)
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.34 2023/10/21 14:33:20 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.18.2
@


1.34
log
@py-ruamel-yaml: updated to 0.17.40

0.17.40
- flow style sets are now preserved ( `!!set {a, b, c} )`. Any values specified when
  loading are dropped, including `!!null ""`.
- |
  potential workaround for issue 484: the long_description_content_type including the variant specification `CommonMark`
  can result in problems on Azure. If you can install from `.tar.gz` using
  `RUAMEL_NO_LONG_DESCRIPTION=1 pip install ruamel.yaml --no-binary :all:` then the long description, and its
  offending type, are nog included (in the METADATA).
  (Reported by [Coury Ditch](https://sourceforge.net/u/cmditch/profile/))
- links in documentation update (reported by [David Hoese](https://sourceforge.net/u/daveydave400/profile/))
- Added some `__repr__` for internally used classes
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.33 2023/10/20 11:10:13 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.17.40
d13 2
d21 1
a21 1
.include "../../lang/python/egg.mk"
@


1.33
log
@py-ruamel-yaml: updated to 0.17.39

0.17.39:
- update README generation, no code changes

0.17.36:
- fixed issue 480, dumping of a loaded empty flow-style mapping with comment failed
- fixed issue 482, caused by DEFAULT_MAPPING_TAG having changes to being a `Tag()`
  instance, not a string
- updated documentation to use mkdocs
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.32 2023/10/04 11:39:18 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.17.39
@


1.32
log
@py-ruamel-yaml: updated to 0.17.35

0.17.35
- support for loading dataclasses with ``InitVar`` variables (some
  special coding was necessary to get the, unexecpected, default value
  in the corresponding instance attribute ( example of usage in
  `this question <https://stackoverflow.com/q/77228378/1307905>`__ )

0.17.34
- Python 3.12 also loads C version when using `typ='safe'`
- initial support for loading invoking `__post_init__()` on dataclasses that have that method
  after loading a registered dataclass (`@@yaml.register_class\n@@dataclass\nclass ...`).
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.31 2023/09/28 15:49:49 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.17.35
@


1.31
log
@py-ruamel-yaml: updated to 0.17.33

0.17.33
- added `flow_seq_start`, `flow_seq_end`, `flow_seq_separator`, `flow_map_start`, `flow_map_end`,
  `flow_map_separator` **class** attributes to the `Emitter` class so flow style output
  can more easily be influenced
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.30 2023/06/17 12:12:36 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.17.33
d9 1
a9 1
HOMEPAGE=	https://sourceforge.net/p/ruamel-yaml/
d13 1
a13 1
DEPENDS+=	${PYPKGPREFIX}-ruamel-yaml-clib>=0.2.6:../../devel/py-ruamel-yaml-clib
@


1.30
log
@py-ruamel-yaml: updated to 0.17.32

0.17.32
- fix issue with scanner getting stuck in infinite loop
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.29 2023/06/06 10:46:01 wiz Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.17.32
@


1.29
log
@py-ruamel-yaml: update to 0.17.31.

[0, 17, 31]: 2023-05-31
  - added tag.setter on `ScalarEvent` and on `Node`, that takes either
    a `Tag` instance, or a str
    (reported by `Sorin Sbarnea <https://sourceforge.net/u/ssbarnea/profile/>`__)

[0, 17, 30]: 2023-05-30
  - fix issue 467, caused by Tag instances not being hashable (reported by
    `Douglas Raillard
    <https://bitbucket.org/%7Bcf052d92-a278-4339-9aa8-de41923bb556%7D/>`__)

[0, 17, 29]: 2023-05-30
  - changed the internals of the tag property from a string to a class which allows
    for preservation of the original handle and suffix. This should
    result in better results using documents with %TAG directives, as well
    as preserving URI escapes in tag suffixes.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.28 2023/05/30 07:58:41 wiz Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.17.31
@


1.28
log
@py-ruamel-yaml: update to 0.17.28.

[0, 17, 28]: 2023-05-26
  - fix for issue 464: documents ending with document end marker without final newline
    fail to load (reported by `Mariusz Rusiniak <https://sourceforge.net/u/r2dan/profile/>`__)

[0, 17, 27]: 2023-05-25
  - fix issue with inline mappings as value for merge keys
    (reported by Sirish on `StackOverflow <https://stackoverflow.com/q/76331049/1307905>`__)
  - fix for 468, error inserting after accessing merge attribute on ``CommentedMap``
    (reported by `Bastien gerard <https://sourceforge.net/u/bagerard/>`__)
  - fix for issue 461 pop + insert on same `CommentedMap` key throwing error
    (reported by `John Thorvald Wodder II <https://sourceforge.net/u/jwodder/profile/>`__)
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.27 2023/05/10 05:19:29 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.17.28
@


1.27
log
@py-ruamel-yaml: updated to 0.17.26

0.17.26
- Fix for error on edge cage for issue 459

0.17.25
- fix for regression while dumping wrapped strings with too many backslashes removed
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.26 2023/05/07 08:40:15 wiz Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.17.26
@


1.26
log
@py-ruamel-yaml: update to 0.17.24.

[0, 17, 24]: 2023-05-06
  - rewrite of ``CommentedMap.insert()``. If you have a merge key in
    the YAML document for the mapping you insert to, the position value should
    be the one as you look at the YAML input.
    This fixes issue 453 where other
    keys of a merged in mapping would show up after an insert (reported by
    `Alex Miller <https://sourceforge.net/u/millerdevel/profile/>`__). It
    also fixes a call to `.insert()` resulting into the merge key to move
    to be the first key if it wasn't already and it is also now possible
    to insert a key before a merge key (even if the fist key in the mapping).
  - fix (in the pure Python implementation including default) for issue 447.
    (reported by `Jack Cherng <https://sourceforge.net/u/jfcherng/profile/>`__,
    also brought up by brent on
    `StackOverflow <https://stackoverflow.com/q/40072485/1307905>`__)

[0, 17, 23]: 2023-05-05
  - fix 458, error on plain scalars starting with word longer than width.
    (reported by `Kyle Larose <https://sourceforge.net/u/klarose/profile/>`__)
  - fix for ``.update()`` no longer correctly handling keyword arguments
    (reported by John Lin on <StackOverflow
    `<https://stackoverflow.com/q/76089100/1307905>`__)
  - fix issue 454: high Unicode (emojis) in quoted strings always
    escaped (reported by `Michal Čihař <https://sourceforge.net/u/nijel/profile/>`__
    based on a question on StackOverflow).
  - fix issue with emitter conservatively inserting extra backslashes in wrapped
    quoted strings (reported by thebenman on `StackOverflow
    <https://stackoverflow.com/q/75631454/1307905>`__)
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.25 2023/05/04 17:23:59 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.17.24
@


1.25
log
@py-ruamel-yaml: updated to 0.17.22

0.17.22
- fix issue 449 where the second exclamation marks got URL encoded (reported
  and fixing PR provided by `John Stark <https://sourceforge.net/u/jods/profile/>`__)
- fix issue with indent != 2 and literal scalars with empty first line
  (reported by wrdis on `StackOverflow <https://stackoverflow.com/q/75584262/1307905>`__)
- updated __repr__ of CommentedMap, now that Python's dict is ordered -> no more
  ordereddict(list-of-tuples)
- merge MR 4, handling OctalInt in YAML 1.1
  (provided by `Jacob Floyd <https://sourceforge.net/u/cognifloyd/profile/>`_)
- fix loading of `!!float 42` (reported by Eric on
  `Stack overflow <https://stackoverflow.com/a/71555107/1307905>`_)
- line numbers are now set on `CommentedKeySeq` and `CommentedKeyMap` (which
  are created if you have a sequence resp. mapping as the key in a mapping)
- plain scalars: put single words longer than width on a line of their own, instead
  of after the previous line (issue 427, reported by `Antoine Cotten
  <https://sourceforge.net/u/antoineco/profile/>`_). Caveat: this currently results in a
  space ending the previous line.
- fix for folded scalar part of 421: comments after ">" on first line of folded
  scalars are now preserved (as were those in the same position on literal scalars).
  Issue reported by Jacob Floyd.
- added stacklevel to warnings
- typing changed from Py2 compatible comments to Py3, removed various Py2-isms
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.24 2022/02/12 17:55:10 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.17.22
@


1.24
log
@py-ruamel-yaml: updated to 0.17.21

0.17.21:
- fix bug in calling `.compose()` method with `pathlib.Path` instance.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.23 2022/01/04 20:53:37 wiz Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.17.21
d13 1
a13 1
DEPENDS+=	${PYPKGPREFIX}-ruamel-yaml-clib>=0.1.2:../../devel/py-ruamel-yaml-clib
@


1.23
log
@*: bump PKGREVISION for egg.mk users

They now have a tool dependency on py-setuptools instead of a DEPENDS
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.22 2022/01/04 12:35:59 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.17.20
a4 1
PKGREVISION=	1
@


1.22
log
@py-ruamel-yaml: updated to 0.17.20

0.17.20
- fix error in microseconds while rounding datetime fractions >= 9999995

0.17.19
- fix mypy problems

0.17.18
- copy-paste error in folded scalar comment attachment
- fix 411, indent error comment between key empty seq value
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.21 2021/11/07 14:51:18 adam Exp $
d5 1
@


1.21
log
@py-ruamel-yaml: updated to 0.17.17

0.17.17
- extract timestamp matching/creation to util
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.20 2021/10/02 18:30:59 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.17.17
@


1.20
log
@py-ruamel-yaml: updated to 0.17.16

0.17.16:
- also handle issue 397 when comment is newline
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.19 2021/08/29 08:42:13 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.17.16
@


1.19
log
@py-ruamel-yaml: updated to 0.17.15

0.17.15:
- fix issue 397, insert comment before key when a comment between key and value exists
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.18 2021/08/26 07:30:05 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.17.15
@


1.18
log
@py-ruamel-yaml: updated to 0.17.14

[0, 17, 14]: 2021-08-25
  - fix issue 396, inserting key/val in merged-in dictionary (reported by `Bastien gerard
    <https://sourceforge.net/u/bagerard/>`__)

[0, 17, 13]: 2021-08-21
  - minor fix in attr handling

[0, 17, 12]: 2021-08-21
  - fix issue with anchor on registered class not preserved and those classes using package
    attrs with `@@attr.s()` (both reported by `ssph <https://sourceforge.net/u/sph/>`__)

[0, 17, 11]: 2021-08-19
  - fix error baseclass for ``DuplicateKeyErorr`` (reported by `Łukasz Rogalski
    <https://sourceforge.net/u/lrogalski/>`__)
  - fix typo in reader error message, causing `KeyError` during reader error
    (reported by `MTU <https://sourceforge.net/u/mtu/>`__)
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.17 2021/07/09 18:33:40 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.17.14
@


1.17
log
@py-ruamel-yaml: updated to 0.17.10

0.17.10 (2021-06-24):
fix issue 388, token with old comment structure != two elements

0.17.9 (2021-06-10):
fix issue with updating CommentedMap

0.17.8 (2021-06-09):
fix for issue 387 where templated anchors on tagged object did get set resulting in potential id reuse.

0.17.7 (2021-05-31):
issue 385 also affected other deprecated loaders

0.17.6 (2021-05-31):
merged type annotations update provided by Jochen Sprickerhof
fix for issue 385: deprecated round_trip_loader function not working
wasted a few hours getting rid of mypy warnings/errors

0.17.5 (2021-05-30):
fix for issue 384 !!set with aliased entry resulting in broken YAML on rt

0.17.4 (2021-04-07):
prevent (empty) comments from throwing assertion error (issue 351 reported by William Kimball) comments (or empty line) will be dropped

0.17.3 (2021-04-07):
fix for issue 382 caused by an error in a format string
allow expansion of aliases by setting yaml.composer.return_alias = lambda s: copy.deepcopy(s)

0.17.2 (2021-03-29):
change -py2.py3-none-any.whl to -py3-none-any.whl, and remove 0.17.1

0.17.1 (2021-03-29):
added ‘Programming Language :: Python :: 3 :: Only’, and removing 0.17.0 from PyPI

0.17.0 (2021-03-26):
removed because of incomplete classifiers
this release no longer supports Python 2.7, most if not all Python 2 specific code is removed. The 0.17.x series is the last to support Python 3.5 (this also allowed for removal of the dependency on ruamel.std.pathlib)
remove Python2 specific code branches and adaptations (u-strings)
prepare % code for f-strings using _F
allow PyOxidisation (issue 324 resp. issue 171)
replaced Python 2 compatible enforcement of keyword arguments with ‘*’
the old top level functions load, safe_load, round_trip_load, dump, safe_dump, round_trip_dump, scan, parse, compose, emit, serialize as well as their _all variants for multi-document streams, now issue a PendingDeprecationning (e.g. when run from pytest, but also Python is started with -Wd). Use the methods on YAML(), which have been extended.
fix for issue 376: indentation changes could put literal/folded scalar to start before the # column of a following comment. Effectively making the comment part of the scalar in the output.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.16 2021/03/05 13:45:28 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.17.10
@


1.16
log
@py-ruamel-yaml: updated to 0.16.13

0.16.13:
- fix for issue 359: could not update() CommentedMap with keyword arguments
- fix for issue 365: unable to dump mutated TimeStamp objects
- fix for issue 371: unable to addd comment without starting space
- fix for issue 373: recursive call to walk_tree not preserving all params
- a None value in a flow-style sequence is now dumped as `null` instead
  of `!!null ''`
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.15 2020/09/05 07:06:43 wiz Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.16.13
a13 4
.include "../../lang/python/pyversion.mk"
.if ${_PYTHON_VERSION} == 27
DEPENDS+=	${PYPKGPREFIX}-ruamel-ordereddict>=0.4.9:../../devel/py-ruamel-ordereddict
.endif
d17 2
@


1.15
log
@py-ruamel-yaml: update to 0.16.12.

Changes not found, but fixes problem with setuptools 50.0.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.14 2020/02/19 09:41:50 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.16.12
@


1.14
log
@py-ruamel-yaml: updated to 0.16.10

[0, 16, 10]:
- (auto) updated image references in README to sourceforge

[0, 16, 9]:
- update CHANGES

[0, 16, 8]:
- update requirements so that ruamel.yaml.clib is installed for 3.8,
  as it has become available (via manylinux builds)

[0, 16, 7]:
- fix typchecking issue on TaggedScalar
- fix error in dumping literal scalar in sequence with comments before element

[0, 16, 6]:
- fix empty string mapping key roundtripping with preservation of quotes as `? ''`
- fix incorrect state setting in class constructor
- adjust deprecation warning test for Hashable, as that no longer warns
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.13 2019/12/17 10:11:28 leot Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.16.10
d9 1
a9 1
HOMEPAGE=	https://bitbucket.org/ruamel/yaml
@


1.13
log
@py-ruamel-yaml: Update to 0.16.5

pkgsrc changes:
 - Remove dependency to py-typing, no longer needed since version 0.14.9
 - Reset USE_LANGUAGES, C parts were splitted in py-ruamel-yaml-clib and a C
   compiler is no longer needed

Changes:
[0, 16, 5]: 2019-08-18
  - allow for ``YAML(typ=['unsafe', 'pytypes'])``

[0, 16, 4]: 2019-08-16
  - fix output of TAG directives with # (reported by `Thomas Smith
    <https://bitbucket.org/%7Bd4c57a72-f041-4843-8217-b4d48b6ece2f%7D/>`__)

[0, 16, 3]: 2019-08-15
  - move setting of version based on YAML directive to scanner, allowing to
    check for file version during TAG directive scanning

[0, 16, 2]: 2019-08-15
  - preserve YAML and TAG directives on roundtrip, correctly output #
    in URL for YAML 1.2 (both reported by `Thomas Smith
    <https://bitbucket.org/%7Bd4c57a72-f041-4843-8217-b4d48b6ece2f%7D/>`__)

[0, 16, 1]: 2019-08-08
  - Force the use of new version of ruamel.yaml.clib (reported by `Alex Joz
    <https://bitbucket.org/%7B9af55900-2534-4212-976c-61339b6ffe14%7D/>`__)
  - Allow '#' in tag URI as these are allowed in YAML 1.2 (reported by
    `Thomas Smith
    <https://bitbucket.org/%7Bd4c57a72-f041-4843-8217-b4d48b6ece2f%7D/>`__)

[0, 16, 0]: 2019-07-25
  - split of C source that generates .so file to ruamel.yaml.clib
  - duplicate keys are now an error when working with the old API as well
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.12 2019/08/23 12:39:24 gdt Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.16.5
d13 1
a13 2
USE_LANGUAGES=	# none

d19 1
a19 1
DEPENDS+=	${PYPKGPREFIX}-ruamel-yaml-clib>=0.1.2:../../devel/py-ruamel-yaml-clib
@


1.12
log
@devel/py-ruamel-yaml: Reset MAINTAINER

(Email to $MAINTAINER did not succeed.)
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.11 2019/08/13 22:50:51 gdt Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.15.100
d13 2
a17 1
DEPENDS+=	${PYPKGPREFIX}-typing-[0-9]*:../../devel/py-typing
d20 2
@


1.11
log
@devel/py-ruamel-yaml: Update to 0.15.100

(While 0.16.1 is current, that update perhaps is more complicated, so
I'm updating to the last release of 0.15 as an intermediate step.)

[0, 15, 100]: 2019-07-17
  - fixing issue with dumping deep-copied data from commented YAML, by
    providing both the memo parameter to __deepcopy__, and by allowing
    startmarks to be compared on their content (reported by `Theofilos
    Petsios
    <https://bitbucket.org/%7Be550bc5d-403d-4fda-820b-bebbe71796d3%7D/>`__)

[0, 15, 99]: 2019-07-12
  - add `py.typed` to distribution, based on a PR submitted by
    `Michael Crusoe
    <https://bitbucket.org/%7Bc9fbde69-e746-48f5-900d-34992b7860c8%7D/>`__
  - merge PR 40 (also by Michael Crusoe) to more accurately specify
    repository in the README (also reported in a misunderstood issue
    some time ago)

[0, 15, 98]: 2019-07-09
  - regenerate ext/_ruamel_yaml.c with Cython version 0.29.12, needed
    for Python 3.8.0b2 (reported by `John Vandenberg
    <https://bitbucket.org/%7B6d4e8487-3c97-4dab-a060-088ec50c682c%7D/>`__)

[0, 15, 97]: 2019-06-06
  - regenerate ext/_ruamel_yaml.c with Cython version 0.29.10, needed for
    Python 3.8.0b1
  - regenerate ext/_ruamel_yaml.c with Cython version 0.29.9, needed for
    Python 3.8.0a4 (reported by `Anthony Sottile
    <https://bitbucket.org/%7B569cc8ea-0d9e-41cb-94a4-19ea517324df%7D/>`__)

[0, 15, 96]: 2019-05-16
  - fix failure to indent comments on round-trip anchored block style
    scalars in block sequence (reported by `William Kimball
    <https://bitbucket.org/%7Bba35ed20-4bb0-46f8-bb5d-c29871e86a22%7D/>`__)

[0, 15, 95]: 2019-05-16
  - fix failure to round-trip anchored scalars in block sequence
    (reported by `William Kimball
    <https://bitbucket.org/%7Bba35ed20-4bb0-46f8-bb5d-c29871e86a22%7D/>`__)
  - wheel files for Python 3.4 no longer provided (`Python 3.4 EOL 2019-03-18
    <https://www.python.org/dev/peps/pep-0429/>`__)
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.10 2019/05/07 09:29:38 adam Exp $
d8 1
a8 1
MAINTAINER=	gde@@llew.me
@


1.10
log
@py-ruamel.yaml: updated to 0.15.94

0.15.94:
- fix missing line-break after end-of-file comments not ending in
  line-break

0.15.93:
- fix failure to parse empty implicit flow mapping key
- in YAML 1.1 plains scalars y, 'n', Y, and 'N' are now
  correctly recognised as booleans and such strings dumped quoted

0.15.92:
- fix failure to parse empty implicit block mapping key

0.15.91:
- allowing duplicate keys would not work for merge keys

0.15.90:
- fix issue with updating CommentedMap from list of tuples

0.15.89:
- fix for items with flow-mapping in block sequence output on single line
- fix for safe dumping erroring in creation of representereror when dumping namedtuple

0.15.88:
- fix inclusing of python code from the subpackage data

0.15.87:
- fix problem with empty lists and the code to reinsert merge keys

0.15.86:
- reinsert merge key in its old position
- fix for issue with non-ASCII anchor names
- fix for issue when parsing flow mapping value starting with colon (in pure Python only)

0.15.85:
- the types used by SafeConstructor for mappings and sequences can
  now by set by assigning to XXXConstructor.yaml_base_dict_type
  (and ..._list_type), preventing the need to copy two methods
  with 50+ lines that had var = {} hardcoded.

0.15.84:
- fix for CommentedMap.copy() not returning CommentedMap, let alone copying comments etc.

0.15.83:
- fix for bug in roundtripping aliases used as key

0.15.82:
- anchors and aliases on scalar int, float, string and bool are now preserved. Anchors
  do not need a referring alias for these
- anchors no longer lost on tagged objects when roundtripping

0.15.81:
 - fix issue saving methods of metaclass derived classes

0.15.80:
 - fix issue emitting BEL character when round-tripping invalid folded input

0.15.79:
- fix issue with anchors nested deeper than alias

0.15.78:
- fix setup issue for 3.8

0.15.77:
- setting yaml.sort_base_mapping_type_on_output = False, will prevent
  explicit sorting by keys in the base representer of mappings. Roundtrip
  already did not do this. Usage only makes real sense for Python 3.6+
- implement Python version check in YAML metadata in _test/test_z_data.py

0.15.76:
- fix issue with empty mapping and sequence loaded as flow-style

0.15.75:
- fix issue with single '?' scalar
- fix issue with duplicate merge keys

0.15.74:
- fix dropping of comment on rt before sequence item that is sequence item

0.15.73:
- fix irregular output on pre-comment in sequence within sequence
- allow non-compact (i.e. next line) dumping sequence/mapping within sequence.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.9 2018/10/14 16:26:51 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.15.94
@


1.9
log
@py-ruamel-yaml: updated to 0.15.72

0.15.72:
- fix regression on explicit 1.1 loading with the C based scanner/parser

0.15.72:
- fix regression on explicit 1.1 loading with the C based scanner/parser

0.15.71:
- fix regression where handcrafted CommentedMaps could not be initiated
- fix regression with non-root literal scalars that needed indent indicator
- tag:yaml.org,2002:python/object/apply now also uses __qualname__ on PY3

0.15.70:
- reverted CommentedMap and CommentedSeq to subclass ordereddict resp. list,
  reimplemented merge maps so that both dict(**commented_map_instance) and JSON
  dumping works. This also allows checking with isinstance() on dict resp. list.

0.15.69:
- fix issue with dump_all gobbling end-of-document comments on parsing

0.15.68:
- fix issue with parsabel, but incorrect output with nested flow-style sequences
- fix issue with loading Python objects that have __setstate__ and recursion in parameters

0.15.67:
- fix issue with extra space inserted with non-root literal strings

0.15.66:
- fix issue with fold indicating characters inserted in safe_load-ed folded strings

0.15.65:
- fix issue 232 revert to throw ParserError for unexcpected ]
  and } instead of IndexError.
- added key and reverse parameter (suggested by Jannik Klemm via email)
- indent root level literal scalars that have directive or document end markers
  at the beginning of a line

0.15.64:
- support round-trip of tagged sequences: !Arg [a, {b: 1}]
- single entry mappings in flow sequences now written by default without quotes
  set yaml.brace_single_entry_mapping_in_flow_sequence=True to force
  getting [a, {b: 1}, {c: {d: 2}}] instead of the default [a, b: 1, c: {d: 2}]
- fix issue when roundtripping floats starting with a dot such as .5

0.15.63:
- small fix only necessary for Windows users that don't use wheels.

0.15.62:
- C based reader/scanner & emitter now allow setting of 1.2 as YAML version.
  ** The loading/dumping is still YAML 1.1 code**, so use the common subset of
  YAML 1.2 and 1.1

0.15.61:
- support for round-tripping folded style scalars
- update of C code
- speed up of scanning (~30% depending on the input)

0.15.60:
- cleanup for mypy
- spurious print in library

0.15.59:
- issue with C based loader and leading zeros

0.15.59:
- issue with C based loader and leading zeros

0.15.58:
- simple mappings can now be used as keys when round-tripping::

    {a: 1, b: 2}: hello world

  although using the obvious operations (del, popitem) on the key will
  fail, you can mutilate it by going through its attributes. If you load the
  above YAML in d, then changing the value is cumbersome:

      d = {CommentedKeyMap([('a', 1), ('b', 2)]): "goodbye"}

  and changing the key even more so:

      d[CommentedKeyMap([('b', 1), ('a', 2)])] = d.pop(
                   CommentedKeyMap([('a', 1), ('b', 2)]))

  (you can use a dict instead of a list of tuples (or ordereddict), but that might result
  in a different order, of the keys of the key, in the output)
- check integers to dump with 1.2 patterns instead of 1.1

0.15.57:
- Fix that CommentedSeq could no longer be used in adding or do a copy

0.15.56:
- fix issue with python -O optimizing away code

0.15.55:
- unmade CommentedSeq a subclass of list. It is now
  indirectly a subclass of the standard
  collections.abc.MutableSequence (without .abc if you are
  still on Python2.7). If you do isinstance(yaml.load('[1, 2]'),
  list)) anywhere in your code replace list with
  MutableSequence.  Directly, CommentedSeq is a subclass of
  the abstract baseclass ruamel.yaml.compat.MutableScliceableSequence,
  with the result that *(extended) slicing is supported on
  CommentedSeq*.
- duplicate keys (or their values) with non-ascii now correctly
  report in Python2, instead of raising a Unicode error.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.8 2018/08/14 14:54:26 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.15.72
d14 1
a14 1
.if ${_PYTHON_VERSION} < 30
a15 2
.endif
.if ${_PYTHON_VERSION} < 35
@


1.8
log
@py-ruamel-yaml: updated to 0.15.54

[0, 15, 54]:
  - fix issue where a comment could pop-up twice in the output
  - fix issue where JSON object (mapping) without spaces was not parsed
    properly
  - fix issue where comments after empty flow-style mappings were not emitted

[0, 15, 53]:
  - fix issue with flow style mapping with comments gobbled newline
  - fix issue where single '+' under YAML 1.2 was interpreted as
    integer, erroring out

[0, 15, 52]:
  - added .copy() mapping representation for round-tripping
    (CommentedMap) to fix incomplete copies of merged mappings
  - Also unmade that class a subclass of ordereddict to solve incorrect behaviour
    for {**merged-mapping} and dict(**merged-mapping)

[0, 15, 51]:
  - Fix method name dumps (were not dotted) and loads (reported by Douglas Raillard
  - Fix spurious trailing white-space caused when the comment start
    column was no longer reached and there was no actual EOL comment
    (e.g. following empty line) and doing substitutions, or when
    quotes around scalars got dropped.

[0, 15, 50]:
  - Allow YAML() as a context manager for output, thereby making it much easier
    to generate multi-documents in a stream.
  - Fix issue with incorrect type information for load() and dump()
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.7 2018/07/13 08:06:39 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.15.54
@


1.7
log
@py-ruamel-yaml: updated to 0.15.43

0.15.43:
merge PR33: Python2.7 on Windows is narrow, but has no sysconfig.get_config_var('Py_UNICODE_SIZE').
register_class() now returns class
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.6 2018/07/03 12:27:03 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.15.43
@


1.6
log
@py-ruamel-yaml: updated to 0.15.42

0.15.42:
fix regression showing only on narrow Python 2.7 (py27mu) builds
run pre-commit tox on Python 2.7 wide and narrow, as well as 3.4/3.5/3.6/3.7/pypy

0.15.41:
add detection of C-compile failure, which was removed while no longer dependent on libyaml, C-extensions compilation still needs a compiler though.

0.15.40:
added links to landing places as suggested in issue 190
fixes issue 201: decoding unicode escaped tags on Python2

0.15.39:
merge P.R.27 improving package startup time (and loading when regexp not actually used)

0.15.38:
fix for losing precision when roundtripping floats
fix for hardcoded dir separator not working for Windows

0.15.37:
again trying to create installable files for 187

0.15.36:
fix issue 187, incompatibility of C extension with 3.7
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.5 2017/12/14 13:21:02 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.15.42
@


1.5
log
@py-ruamel-yaml: updated to 0.15.35

[0, 15, 35]:
- allow None as stream when specifying transform parameters to
  YAML.dump().
  This is useful if the transforming function doesn't return a meaningful value
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.4 2017/10/28 08:51:25 adam Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.15.35
@


1.4
log
@py-ruamel-yaml: updated to 0.15.34

0.15.34:
- fix for issue 157: CDumper not dumping floats
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.3 2017/04/23 15:52:33 leot Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.15.34
@


1.3
log
@Adjust DEPENDS and PLIST

py-ruamel-base is no longer needed and Python < 35 also needs py-typing.
Due the latter, requires.txt is installed also for the py34- version, adjust
PLIST accordingly.

Pointed out by <nils>'s bulk builds.

Bump PKGREVISION
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.2 2017/04/14 13:05:06 leot Exp $
d3 1
a3 1
DISTNAME=	ruamel.yaml-0.14.6
d5 1
a5 2
PKGREVISION=	1
CATEGORIES=	devel
a12 2
PLIST_VARS+=	pyreq

a15 1
PLIST.pyreq=	yes
a18 1
PLIST.pyreq=	yes
a20 1
.include "../../lang/python/application.mk"
@


1.2
log
@Update devel/py-ruamel-yaml to 0.14.6

Changes:
[0, 14, 6]: 2017-04-14
  - binary, octal and hex integers are now preserved by default. This
    was a known deficiency. Working on this was prompted by the issue report (112)
    from devnoname120, as well as the additional experience with `.replace()`
    on `scalarstring` classes.
  - fix issues 114: cannot install on Buildozer (reported by mixmastamyk).
    Setting env. var ``RUAMEL_NO_PIP_INSTALL_CHECK`` will suppress ``pip``-check.

[0, 14, 5]: 2017-04-04
  - fix issue 109: None not dumping correctly at top level (reported by Andrea Censi)
  - fix issue 110: .replace on Preserved/DoubleQuoted/SingleQuoted ScalarString
    would give back "normal" string (reported by sandres23)

[0, 14, 4]: 2017-03-31
  - fix readme

[0, 14, 3]: 2017-03-31
  - fix for 0o52 not being a string in YAML 1.1 (reported on
    `StackOverflow Q&A 43138503><http://stackoverflow.com/a/43138503/1307905>`_ by
    `Frank D <http://stackoverflow.com/users/7796630/frank-d>`_

[0, 14, 2]: 2017-03-23
  - fix for old default pip on Ubuntu 14.04 (reported by Sébastien Maccagnoni-Munch)

0.14.1: 2017-03-22
  - fix Text not available on 3.5.0 and 3.5.1 (reported by Charles Bouchard-Légaré)

0.14.0: 2017-03-21
  - updates for mypy --strict
  - preparation for moving away from inheritance in Loader and Dumper, calls from e.g.
    the Representer to the Serializer.serialize() are now done via the attribute
    .serializer.serialize(). Usage of .serialize() outside of Serializer will be
    deprecated soon
  - some extra tests on main.py functions

0.13.14: 2017-02-12
  - fix for issue 97: clipped block scalar followed by empty lines and comment
    would result in two CommentTokens of which the first was dropped.
    (reported by Colm O'Connor)

0.13.13: 2017-01-28
  - fix for issue 96: prevent insertion of extra empty line if indented mapping entries
    are separated by an empty line (reported by Derrick Sawyer)

0.13.11: 2017-01-23
  - allow ':' in flow style scalars if not followed by space. Also don't
    quote such scalar as this is no longer necessary.
  - add python 3.6 manylinux wheel to PyPI

0.13.10: 2017-01-22
  - fix for issue 93, insert spurious blank line before single line comment
    between indented sequence elements (reported by Alex)

0.13.9: 2017-01-18
  - fix for issue 92, wrong import name reported by the-corinthian

0.13.8: 2017-01-18
  - fix for issue 91, when a compiler is unavailable reported by Maximilian Hils
  - fix for deepcopy issue with TimeStamps not preserving 'T', reported on
    `StackOverflow Q&A <http://stackoverflow.com/a/41577841/1307905>`_ by
    `Quuxplusone <http://stackoverflow.com/users/1424877/quuxplusone>`_

0.13.7: 2016-12-27
  - fix for issue 85, constructor.py importing unicode_literals caused mypy to fail
    on 2.7 (reported by Peter Amstutz)

0.13.6: 2016-12-27
  - fix for issue 83, collections.OrderedDict not representable by SafeRepresenter
    (reported by Frazer McLean)

0.13.5: 2016-12-25
  - fix for issue 84, deepcopy not properly working (reported by Peter Amstutz)

0.13.4: 2016-12-05
  - another fix for issue 82, change to non-global resolver data broke implicit type
    specification

0.13.3: 2016-12-05
  - fix for issue 82, deepcopy not working (reported by code monk)

0.13.2: 2016-11-28
  - fix for comments after empty (null) values  (reported by dsw2127 and cokelaer)

0.13.1: 2016-11-22
  - optimisations on memory usage when loading YAML from large files (py3: -50%, py2: -85%)

0.13.0: 2016-11-20
  - if ``load()`` or ``load_all()`` is called with only a single argument
    (stream or string)
    a UnsafeLoaderWarning will be issued once. If appropriate you can surpress this
    warning by filtering it. Explicitly supplying the ``Loader=ruamel.yaml.Loader``
    argument, will also prevent it from being issued. You should however consider
    using ``safe_load()``, ``safe_load_all()`` if your YAML input does not use tags.
  - allow adding comments before and after keys (based on
    `StackOveflow Q&A <http://stackoverflow.com/a/40705671/1307905>`_  by
    `msinn <http://stackoverflow.com/users/7185467/msinn>`_)

0.12.18: 2016-11-16
  - another fix for numpy (re-reported independently by PaulG & Nathanial Burdic)

0.12.17: 2016-11-15
  - only the RoundTripLoader included the Resolver that supports YAML 1.2
    now all loaders do (reported by mixmastamyk)

0.12.16: 2016-11-13
  - allow dot char (and many others) in anchor name
    Fix issue 72 (reported by Shalon Wood)
  - Slightly smarter behaviour dumping strings when no style is
    specified. Single string scalars that start with single quotes
    or have newlines now are dumped double quoted: "'abc\nklm'" instead of::

      '''abc

        klm'''

0.12.14: 2016-09-21
 - preserve round-trip sequences that are mapping keys
   (prompted by stackoverflow question 39595807 from Nowox)

0.12.13: 2016-09-15
 - Fix for issue #60 representation of CommentedMap with merge
   keys incorrect (reported by Tal Liron)

0.12.11: 2016-09-06
 - Fix issue 58 endless loop in scanning tokens (reported by
   Christopher Lambert)

0.12.10: 2016-09-05
 - Make previous fix depend on unicode char width (32 bit unicode support
   is a problem on MacOS reported by David Tagatac)

0.12.8: 2016-09-05
  - To be ignored Unicode characters were not properly regex matched
    (no specific tests, PR by Haraguroicha Hsu)

0.12.7: 2016-09-03
  - fixing issue 54 empty lines with spaces (reported by Alex Harvey)

0.12.6: 2016-09-03
  - fixing issue 46 empty lines between top-level keys were gobbled (but
    not between sequence elements, nor between keys in netsted mappings
    (reported by Alex Harvey)

0.12.5: 2016-08-20
  - fixing issue 45 preserving datetime formatting (submitted by altuin)
    Several formatting parameters are preserved with some normalisation:
  - preserve 'T', 't' is replaced by 'T', multiple spaces between date
    and time reduced to one.
  - optional space before timezone is removed
  - still using microseconds, but now rounded (.1234567 -> .123457)
  - Z/-5/+01:00 preserved

0.12.4: 2016-08-19
  - Fix for issue 44: missing preserve_quotes keyword argument (reported
    by M. Crusoe)

0.12.3: 2016-08-17
  - correct 'in' operation for merged CommentedMaps in round-trip mode
    (implementation inspired by J.Ngo, but original not working for merges)
  - iteration over round-trip loaded mappings, that contain merges. Also
    keys(), items(), values() (Py3/Py2) and iterkeys(), iteritems(),
    itervalues(), viewkeys(), viewitems(), viewvalues() (Py2)
  - reuse of anchor name now generates warning, not an error. Round-tripping such
    anchors works correctly. This inherited PyYAML issue was brought to attention
    by G. Coddut (and was long standing https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515634)
    suppressing the warning::

        import warnings
        from ruamel.yaml.error import ReusedAnchorWarning
        warnings.simplefilter("ignore", ReusedAnchorWarning)

0.12.2: 2016-08-16
  - minor improvements based on feedback from M. Crusoe
    https://bitbucket.org/ruamel/yaml/issues/42/

0.12.0: 2016-08-16
  - drop support for Python 2.6
  - include initial Type information (inspired by M. Crusoe)

0.11.15: 2016-08-07
  - Change to prevent FutureWarning in NumPy, as reported by tgehring
    ("comparison to None will result in an elementwise object comparison in the future")

0.11.14: 2016-07-06
  - fix preserve_quotes missing on original Loaders (as reported
    by Leynos, bitbucket issue 38)

0.11.13: 2016-07-06
  - documentation only, automated linux wheels

0.11.12: 2016-07-06
  - added support for roundtrip of single/double quoted scalars using:
    ruamel.yaml.round_trip_load(stream, preserve_quotes=True)

0.11.10: 2016-05-02
  - added .insert(pos, key, value, comment=None) to CommentedMap

0.11.10: 2016-04-19
  - indent=2, block_seq_indent=2 works as expected

0.11.0: 2016-02-18
  - RoundTripLoader loads 1.2 by default (no sexagesimals, 012 octals nor
    yes/no/on/off booleans
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.1 2016/05/16 13:52:54 nils Exp $
d5 1
d14 1
a14 1
DEPENDS+=	${PYPKGPREFIX}-ruamel-base>=1.0.0:../../devel/py-ruamel-base
a15 1
# for python < 3.0
d19 5
@


1.1
log
@Initial import of py-ruamel-yaml, version 0.10.23,
into the NetBSD Packages Collection.

ruamel.yaml is a YAML parser/emitter that supports roundtrip preservation
of comments, seq/map flow style, and map key order
@
text
@d1 1
a1 1
# $NetBSD$
d3 2
a4 2
DISTNAME=	ruamel.yaml-0.10.23
PKGNAME=	${PYPKGPREFIX}-ruamel-yaml-0.10.23
@

