gedcomkit 0.1.16__tar.gz → 0.1.18__tar.gz

{gedcomkit-0.1.16 → gedcomkit-0.1.18}/CHANGELOG.md

@@ -5,6 +5,140 @@ format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and
 the project uses semantic versioning within the usual pre-1.0 compatibility
 rules.
 
+## [Unreleased]
+
+## [0.1.18] - 2026-10-16
+
+### Added
+
+- `validate::inspect` runs nine more checks. Each has a stable name, and
+  the module documentation now lists every check with its severity:
+  - `married-after-died` (contradiction): a family's first `MARR` wholly
+    after a partner's death, or, failing a dated death, their burial. A
+    burial before the wedding beside a death after it is no finding here:
+    the death says when the life ended, and the burial is
+    `buried-before-died`'s.
+  - `child-born-long-after-father-died`: a child born more than 300 days
+    after the death of the family's `HUSB`. A contradiction when both dates
+    name a day; a question otherwise, since a bare year is often a guess.
+  - `christened-before-born` (contradiction): a `CHR`, `CHRA` or `BAPM`
+    wholly before the birth.
+  - `event-before-birth`: the mirror of `event-after-death`, for any other
+    event or attribute wholly before the birth year. A burial or cremation
+    is left to `died-before-born` and `buried-before-died` when the person
+    has a dated death.
+  - `buried-long-after-died` (question): a burial more than 365 days after
+    the death, counted from the latest day the death allows to the earliest
+    the burial does.
+  - `children-too-close`: two children of one mother born 2 to 270 days
+    apart. A contradiction when both dates name a day and are under 150
+    days apart; a question otherwise, since a very early birth makes the
+    longer gaps possible. A mother's children are taken from every family
+    she is the `WIFE` in; a family with no `WIFE` is compared alone.
+  - `possible-duplicate-child` (question): two children of one mother with
+    one given name (one name may be the start of the other: `Mira` and
+    `Mira Elowen`, but not `Mira Elowen` and `Mira Rose`), born on one
+    date, or on one day and month of different years.
+  - `conflicting-vitals` (question): two `BIRT`, or two `DEAT`, events of
+    one person that cannot both be true, even with an approximate date
+    allowed a year either way (`BIRT 1851` and `BIRT ABT 1850` are not in
+    conflict). GEDCOM lets a file record alternatives with the preferred
+    first, which is the one the other checks read, so this asks rather
+    than accuses.
+  - `own-ancestor` (contradiction): a loop in the parent links, read from
+    both directions of the family link as `FamilyGraph` reads them. One
+    finding per loop, on the person in it the file lists first, naming the
+    shortest way round: in full up to six steps, and past that its first
+    five and how many more, so a loop through 20,000 people is one short
+    message.
+
+  The three checks that compare pairs are bounded, so a hostile file cannot
+  make the report as large as the square of its people. `children-too-close`
+  and `possible-duplicate-child` report at most ten pairs for one mother,
+  and `conflicting-vitals` ten for one person's births and ten for their
+  deaths, the first in the order the file lists them; one more finding under
+  the same check, as serious as the most serious pair it stands for, then
+  says how many more pairs there are and how many in all (`4059990 more
+  pairs of children born 2 to 270 days apart, 4060000 in all`). The work is
+  bounded too: births and deaths are counted by sorting rather than compared
+  pair by pair; children who share a span of birth days, or a given name,
+  are compared as one group; and one mother's children are compared at most
+  100,000 times for each check, past which the summary gives its counts as
+  lower bounds. A family of 3,000 children of one name born in one month,
+  which made 4.5 million sibling findings, makes 22; a person with 5,000
+  births, which made 12.5 million `conflicting-vitals` findings, makes 11.
+
+### Changed
+
+- PyPI gets one wheel, Linux x86_64, beside the source distribution. The
+  macOS and Windows wheels are no longer cross-built; on those platforms pip
+  builds from the sdist, which needs a Rust toolchain.
+- `died-before-born`, `buried-before-died`, `christened-before-born`,
+  `married-after-died` and `conflicting-vitals` compare as finely as both
+  dates allow: a burial on 12 September before a death on 14 September of
+  one year is now found. Julian and Gregorian dates are put on one count of days first.
+  An approximate date (`ABT`, `CAL`, `EST`) still vouches for its year and
+  nothing finer, and a bound (`BEF`, `AFT`, `BET`) admits its own day. A
+  finding the years alone decide keeps its wording (`born 1900 and died
+  1880`); one only a finer comparison finds names the dates in full
+  (`died 14 September 1862 and buried 12 September 1862`).
+- An approximate date (`ABT`, `CAL`, `EST`) may be a year out. A finding
+  that two events are out of order is a question, not a contradiction, when
+  moving each approximate date a year either way could put them in order:
+  `BIRT ABT 1850` with `CHR 1849` or `CENS 1849`, or `DEAT ABT 1850` with a
+  burial in 1849. Two years out it is still a contradiction. This holds for
+  `died-before-born`, `buried-before-died`, `event-after-death`,
+  `married-before-born` and `child-born-after-mother-died`, and for the new
+  `christened-before-born`, `event-before-birth` and `married-after-died`;
+  the checks about an age or an interval take an approximate year as
+  written. Their messages say an approximate date is one: `born about 1850,
+  and Christening is dated 1849`.
+- `event-after-death` is a question, not a contradiction, for an `EVEN` or
+  `FACT`. Such an event is whatever its free-text `TYPE` says — a land
+  entry completed, a patent issued, an estate settled — and many of those
+  are done in a dead person's name. The other events keep their severity.
+- `by` is read as a `BEF` qualifier: `by 5 October 1752` is
+  `BEF 5 OCT 1752`, where it was read as 5 May 1752. The qualifiers the
+  reader already knew (`abt`, `about`, `c.`, `ca.`, `bef`, `before`, `aft`,
+  `after`, and the others) are unchanged.
+
+### Fixed
+
+- The date reader no longer shifts the pieces of a four-word date around a
+  word it does not know. `chr 10 Nov 1788` read as 10 October 1788,
+  `b 9 Jun 1750` as 9 September, `bapt. 3 May 1801` as 3 March: the leading
+  word was tried as a month, failed, and the day number was taken as the
+  month instead. Four pieces are now read only as a day, its ordinal ending
+  and a month written as a word, in either order (`Feb 11 th 1809`,
+  `11 th Feb 1809`, `1er janvier 1800`, `5te Januar 1800`); anything else is
+  `DateKind::Unparsed`, keeps its text as the phrase, and still offers its
+  year to sort by, so `to_gedcom_5_5_1` and `to_gedcom_7` return `None` and
+  the caller writes it as a date phrase. A month given only as a number never
+  decides the order of four pieces.
+- A dual year (`10 JAN 1731/32`) admits both its years in every check, not
+  only where days are compared. The checks that compare years read it as
+  its first year alone, so `BIRT 1732` with `DEAT 10 JAN 1731/32` was
+  `died-before-born` ("born 1732 and died 1731"); it is now no finding, and
+  a death past both years says `died between 1731 and 1732`. Where the days
+  of two dates are compared, they alone decide the order, so a burial in the
+  Julian year 1700, which runs eleven days into the Gregorian 1701, is no
+  longer wholly before a death in the Gregorian 1701.
+- `child-listed-twice` keeps the children it has seen in a set rather than
+  a list, so a family listing tens of thousands of children is checked in
+  time proportional to their number, not its square.
+- The checks on an individual's own record read that record's dates when it
+  has no identifier, or shares one with another record. Before, such a
+  record was checked against no dates, or against those of the last record
+  with its identifier.
+
+## [0.1.17] - 2026-10-16
+
+### Changed
+
+- Relicensed from AGPL-3.0-or-later to GPL-3.0-or-later: the crate, the
+  Python wheel and the npm package. The code is unchanged. Versions up to and
+  including 0.1.16 remain available under AGPL-3.0-or-later as published.
+
 ## [0.1.16] - 2026-10-14
 
 ### Added

{gedcomkit-0.1.16 → gedcomkit-0.1.18}/Cargo.lock

@@ -35,7 +35,7 @@ dependencies = [
 
 [[package]]
 name = "gedcomkit"
-version = "0.1.16"
+version = "0.1.18"
 dependencies = [
  "flate2",
  "serde",

{gedcomkit-0.1.16 → gedcomkit-0.1.18}/Cargo.toml

@@ -3,7 +3,7 @@
 # was checked on crates.io, npm, and PyPI before the initial release.
 [package]
 name = "gedcomkit"
-version = "0.1.16"
+version = "0.1.18"
 description = "A byte-preserving GEDCOM document model: decoding, parsing, readings, version conversion, plausibility checks, and the GEDZIP container, for GEDCOM 5.5 through 7.x."
 edition = "2024"
 # The true minimum, not the workspace's toolchain: a parser library is a leaf
@@ -11,10 +11,11 @@ edition = "2024"
 # actually needs a newer feature (currently: edition 2024, `slice::as_chunks`).
 rust-version = "1.88"
 # The crate carries its own license so it can leave the (unlicensed)
-# application workspace. AGPL-3.0-or-later, the user's call (2026-09-07):
+# application workspace. GPL-3.0-or-later, the user's call (2026-10-16; AGPL
+# through 0.1.16):
 # the LICENSE text sits beside this file, and the sole copyright holder can
 # always grant other terms separately.
-license = "AGPL-3.0-or-later"
+license = "GPL-3.0-or-later"
 repository = "https://gitlab.com/timrs2998/gedcomkit"
 keywords = ["gedcom", "genealogy", "parser", "family-tree", "gedzip"]
 categories = ["parser-implementations", "encoding"]

{gedcomkit-0.1.16/bindings/gedcomkit-py → gedcomkit-0.1.18}/LICENSE

@@ -1,5 +1,5 @@
-                    GNU AFFERO GENERAL PUBLIC LICENSE
-                       Version 3, 19 November 2007
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
 
  Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
  Everyone is permitted to copy and distribute verbatim copies
@@ -7,15 +7,17 @@
 
                             Preamble
 
-  The GNU Affero General Public License is a free, copyleft license for
-software and other kinds of works, specifically designed to ensure
-cooperation with the community in the case of network server software.
+  The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
 
   The licenses for most software and other practical works are designed
 to take away your freedom to share and change the works.  By contrast,
-our General Public Licenses are intended to guarantee your freedom to
+the GNU General Public License is intended to guarantee your freedom to
 share and change all versions of a program--to make sure it remains free
-software for all its users.
+software for all its users.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  You can apply it to
+your programs, too.
 
   When we speak of free software, we are referring to freedom, not
 price.  Our General Public Licenses are designed to make sure that you
@@ -24,34 +26,44 @@ them if you wish), that you receive source code or can get it if you
 want it, that you can change the software or use pieces of it in new
 free programs, and that you know you can do these things.
 
-  Developers that use our General Public Licenses protect your rights
-with two steps: (1) assert copyright on the software, and (2) offer
-you this License which gives you legal permission to copy, distribute
-and/or modify the software.
-
-  A secondary benefit of defending all users' freedom is that
-improvements made in alternate versions of the program, if they
-receive widespread use, become available for other developers to
-incorporate.  Many developers of free software are heartened and
-encouraged by the resulting cooperation.  However, in the case of
-software used on network servers, this result may fail to come about.
-The GNU General Public License permits making a modified version and
-letting the public access it on a server without ever releasing its
-source code to the public.
-
-  The GNU Affero General Public License is designed specifically to
-ensure that, in such cases, the modified source code becomes available
-to the community.  It requires the operator of a network server to
-provide the source code of the modified version running there to the
-users of that server.  Therefore, public use of a modified version, on
-a publicly accessible server, gives the public access to the source
-code of the modified version.
-
-  An older license, called the Affero General Public License and
-published by Affero, was designed to accomplish similar goals.  This is
-a different license, not a version of the Affero GPL, but Affero has
-released a new version of the Affero GPL which permits relicensing under
-this license.
+  To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too, receive
+or can get the source code.  And you must show them these terms so they
+know their rights.
+
+  Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+  For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+  Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+  Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
 
   The precise terms and conditions for copying, distribution and
 modification follow.
@@ -60,7 +72,7 @@ modification follow.
 
   0. Definitions.
 
-  "This License" refers to version 3 of the GNU Affero General Public License.
+  "This License" refers to version 3 of the GNU General Public License.
 
   "Copyright" also means copyright-like laws that apply to other kinds of
 works, such as semiconductor masks.
@@ -537,45 +549,35 @@ to collect a royalty for further conveying from those to whom you convey
 the Program, the only way you could satisfy both those terms and this
 License would be to refrain entirely from conveying the Program.
 
-  13. Remote Network Interaction; Use with the GNU General Public License.
-
-  Notwithstanding any other provision of this License, if you modify the
-Program, your modified version must prominently offer all users
-interacting with it remotely through a computer network (if your version
-supports such interaction) an opportunity to receive the Corresponding
-Source of your version by providing access to the Corresponding Source
-from a network server at no charge, through some standard or customary
-means of facilitating copying of software.  This Corresponding Source
-shall include the Corresponding Source for any work covered by version 3
-of the GNU General Public License that is incorporated pursuant to the
-following paragraph.
+  13. Use with the GNU Affero General Public License.
 
   Notwithstanding any other provision of this License, you have
 permission to link or combine any covered work with a work licensed
-under version 3 of the GNU General Public License into a single
+under version 3 of the GNU Affero General Public License into a single
 combined work, and to convey the resulting work.  The terms of this
 License will continue to apply to the part which is the covered work,
-but the work with which it is combined will remain governed by version
-3 of the GNU General Public License.
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
 
   14. Revised Versions of this License.
 
   The Free Software Foundation may publish revised and/or new versions of
-the GNU Affero General Public License from time to time.  Such new versions
-will be similar in spirit to the present version, but may differ in detail to
+the GNU General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
 address new problems or concerns.
 
   Each version is given a distinguishing version number.  If the
-Program specifies that a certain numbered version of the GNU Affero General
+Program specifies that a certain numbered version of the GNU General
 Public License "or any later version" applies to it, you have the
 option of following the terms and conditions either of that numbered
 version or of any later version published by the Free Software
 Foundation.  If the Program does not specify a version number of the
-GNU Affero General Public License, you may choose any version ever published
+GNU General Public License, you may choose any version ever published
 by the Free Software Foundation.
 
   If the Program specifies that a proxy can decide which future
-versions of the GNU Affero General Public License can be used, that proxy's
+versions of the GNU General Public License can be used, that proxy's
 public statement of acceptance of a version permanently authorizes you
 to choose that version for the Program.
 
@@ -633,29 +635,40 @@ the "copyright" line and a pointer to where the full notice is found.
     Copyright (C) <year>  <name of author>
 
     This program is free software: you can redistribute it and/or modify
-    it under the terms of the GNU Affero General Public License as published by
+    it under the terms of the GNU General Public License as published by
     the Free Software Foundation, either version 3 of the License, or
     (at your option) any later version.
 
     This program is distributed in the hope that it will be useful,
     but WITHOUT ANY WARRANTY; without even the implied warranty of
     MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-    GNU Affero General Public License for more details.
+    GNU General Public License for more details.
 
-    You should have received a copy of the GNU Affero General Public License
+    You should have received a copy of the GNU General Public License
     along with this program.  If not, see <https://www.gnu.org/licenses/>.
 
 Also add information on how to contact you by electronic and paper mail.
 
-  If your software can interact with users remotely through a computer
-network, you should also make sure that it provides a way for users to
-get its source.  For example, if your program is a web application, its
-interface could display a "Source" link that leads users to an archive
-of the code.  There are many ways you could offer source, and different
-solutions will be better for different programs; see section 13 for the
-specific requirements.
+  If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+    <program>  Copyright (C) <year>  <name of author>
+    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
 
   You should also get your employer (if you work as a programmer) or school,
 if any, to sign a "copyright disclaimer" for the program, if necessary.
-For more information on this, and how to apply and follow the GNU AGPL, see
+For more information on this, and how to apply and follow the GNU GPL, see
 <https://www.gnu.org/licenses/>.
+
+  The GNU General Public License does not permit incorporating your program
+into proprietary programs.  If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.  But first, please read
+<https://www.gnu.org/licenses/why-not-lgpl.html>.

{gedcomkit-0.1.16 → gedcomkit-0.1.18}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: gedcomkit
-Version: 0.1.16
+Version: 0.1.18
 Classifier: Development Status :: 3 - Alpha
 Classifier: Programming Language :: Rust
 Classifier: Programming Language :: Python :: Implementation :: CPython
@@ -8,7 +8,7 @@ Classifier: Topic :: Sociology :: Genealogy
 License-File: LICENSE
 Summary: An archival-grade GEDCOM library: byte-preserving round-trip, encoding detection and reporting, GEDCOM 5.5 through 7.x, GEDZIP. Rust core, Python bindings.
 Keywords: gedcom,genealogy,parser,family-tree,gedzip
-License-Expression: AGPL-3.0-or-later
+License-Expression: GPL-3.0-or-later
 Requires-Python: >=3.9
 Description-Content-Type: text/markdown; charset=UTF-8; variant=GFM
 
@@ -52,5 +52,5 @@ maturin build --release  # a wheel
 The Rust core lives at the root of the same repository; this crate
 is a thin PyO3 layer over its public API.
 
-License: AGPL-3.0-or-later, the same as the core (see LICENSE).
+License: GPL-3.0-or-later, the same as the core (see LICENSE).
 

{gedcomkit-0.1.16 → gedcomkit-0.1.18}/README.md

@@ -23,6 +23,9 @@ Python:
 python -m pip install gedcomkit
 ```
 
+Wheels are published for Linux x86_64 only. Elsewhere pip builds the package from
+source, which needs a Rust toolchain ([rustup](https://rustup.rs)).
+
 Node.js / WASM:
 
 ```bash
@@ -161,7 +164,7 @@ and don't need the original bytes to survive.
 | Hostile-input bounds | size, depth, counts | file size | — | — |
 | Version conversion | reported per construct | — | — | — |
 | Python + browser bindings | yes | — | JS only | — |
-| License | AGPL-3.0-or-later | MIT | MIT | MIT |
+| License | GPL-3.0-or-later | MIT | MIT | MIT |
 
 ## How it is tested
 
@@ -214,10 +217,11 @@ contributors are expected to follow.
 
 ## License
 
-**AGPL-3.0-or-later** (see [LICENSE](LICENSE)). In short: use, study, and
-change it freely; if you distribute it — or run a modified copy as a network
-service — pass the same freedoms on, source included. The copyright holder
-can grant separate terms; open an issue to ask.
+**GPL-3.0-or-later** (see [LICENSE](LICENSE)). In short: use, study, and
+change it freely; if you distribute it, or anything built on it, pass the
+same freedoms on, source included. Versions up to 0.1.16 were published
+under AGPL-3.0-or-later. The copyright holder can grant separate terms; open
+an issue to ask.
 
 The library's code is original to this project. What it learned from
 elsewhere, it learned as published fact — the GEDCOM specifications' tag and

{gedcomkit-0.1.16 → gedcomkit-0.1.18}/bindings/gedcomkit-py/Cargo.lock

@@ -35,7 +35,7 @@ dependencies = [
 
 [[package]]
 name = "gedcomkit"
-version = "0.1.16"
+version = "0.1.18"
 dependencies = [
  "flate2",
  "serde",
@@ -43,7 +43,7 @@ dependencies = [
 
 [[package]]
 name = "gedcomkit-py"
-version = "0.1.16"
+version = "0.1.18"
 dependencies = [
  "gedcomkit",
  "pyo3",

{gedcomkit-0.1.16 → gedcomkit-0.1.18}/bindings/gedcomkit-py/Cargo.toml

@@ -2,11 +2,11 @@
 # abi3 keeps it to one wheel per platform across Python versions.
 [package]
 name = "gedcomkit-py"
-version = "0.1.16"
+version = "0.1.18"
 description = "Python bindings for gedcomkit: an archival-grade GEDCOM library — byte-preserving round-trip, encoding detection, GEDCOM 5.5 through 7.x, GEDZIP."
 edition = "2024"
 rust-version = "1.88"
-license = "AGPL-3.0-or-later"
+license = "GPL-3.0-or-later"
 repository = "https://gitlab.com/timrs2998/gedcomkit"
 readme = "README.md"
 publish = false