some games' meta-data contained in .pgn files before loading them to chess database.
PGN files that are being published by tournaments' organizers sometimes (especially for large events where
few people work on digitalizing games) used to be not consistent. E.g. event name or event place is written
in slightly different way or there is missing some important information in .pgn files that we want to have - like
time control, players ELO or titles, etc. Those scripts help to fix and complete this information quickly
(faster than just by manually editing .pgn files).
The idea is to perform following steps:
- import games to SQLite database
- run few SQL queries that check data consistency and things that we care
- based on results of previous step, write fix SQL expressions (usually the ones from previous tournaments
are good enough or needs only slight modification)
- run fix expressions
- re-check data (using queries from second step)
- export games back to .pgn file
- import .pgn file to chess database of your choice (e.g. SCID).
So using this package requires some basic SQL knowledge and some initial time investment into getting
familiar how all this works and creating an initial scripts suitable for your specific use cases.
But my experience is that tournament organizers tend to replicate the same issues in .pgn files
from one event edition to next. So workout scripts from one edition usually works for all next editions of the
same tournament.
Provided examples use POSIX shell and some utilities (like sed), so Linux or Mac users could have good starting point.
Windows users may need to put more time to rewrite this staff to technologies available in their system or
try to use some utilities like cygwin or unix services for windows.
For information what files are deployed by this package and where see file README.md included in source-ball or
in typical installation using pip deployed to folder:
- /usr/local/share/doc/normalizePGN (Linux)
- C:\Python35\doc\normalizePGN (Windows) or
- <USER>\AppData\Local\Programs\Python\Python35-32\Doc\normalizePGN
1 maintainer
Metadata
1 maintainer
Release files for normalizePGN 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| normalizePGN-0.1.1.tar.gz | 754.5 kB | Without provenance | Details for normalizePGN-0.1.1.tar.gz |
Release files / normalizePGN-0.1.1.tar.gz
| Download URL | normalizePGN-0.1.1.tar.gz |
|---|---|
| Size | 754.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d21fbc86bc4d50a52020a52f9feae91d1f3409fe41669026732368020450a797
|
|
BLAKE2b-256 checksum How to use checksums |
a2cf32d69ad14a197827e5d90ec0cd3c230dd2c5517331c67eb5c5f1aeea7d0d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for normalizePGN 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
