json-store 4.4__tar.gz → 4.6__tar.gz

{json_store-4.4 → json_store-4.6}/.gitignore

@@ -1,9 +1,11 @@
 # cache
 *.pyc
+.*_cache
 .cache
 __pycache__
 
 # dev/test
+.envrc
 .venv*
 .python-version
 .tox

{json_store-4.4 → json_store-4.6}/LICENSE.txt

@@ -1,4 +1,4 @@
-Copyright (c) 2010-2025 Jeremy Avnet
+Copyright (c) 2010-2026 Jeremy Avnet
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

{json_store-4.4 → json_store-4.6}/PKG-INFO

@@ -1,13 +1,13 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.5
 Name: json-store
-Version: 4.4
+Version: 4.6
 Summary: A shelve-like store using JSON serialization.
 Project-URL: Homepage, https://github.com/brainsik/json-store
 Project-URL: Repository, https://github.com/brainsik/json-store.git
 Project-URL: Issues, https://github.com/brainsik/json-store/issues
 Project-URL: Changelog, https://github.com/brainsik/json-store/releases
 Author-email: jeremy avnet <json-store@theory.org>
-License: Copyright (c) 2010-2025 Jeremy Avnet
+License: Copyright (c) 2010-2026 Jeremy Avnet
         
         Permission is hereby granted, free of charge, to any person obtaining a copy
         of this software and associated documentation files (the "Software"), to deal
@@ -33,28 +33,28 @@ Classifier: Intended Audience :: Developers
 Classifier: License :: OSI Approved :: MIT License
 Classifier: Operating System :: OS Independent
 Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
 Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Python :: 3.15
 Classifier: Programming Language :: Python :: Implementation :: CPython
 Classifier: Programming Language :: Python :: Implementation :: PyPy
 Classifier: Topic :: Software Development :: Libraries
-Requires-Python: >=3.10
+Requires-Python: >=3.11
 Description-Content-Type: text/markdown
 
-# JSON Store
+# json-store
 
 [![json-store](https://github.com/brainsik/json-store/actions/workflows/main.yml/badge.svg)](https://github.com/brainsik/json-store/actions/workflows/main.yml)
 ![PyPI](https://img.shields.io/pypi/v/json-store)
 ![PyPI - Python Version](https://img.shields.io/pypi/pyversions/json-store)
 
-JSON store is a simple replacement for shelve. It writes JSON serialized files,
+**json-store** is a simple replacement for shelve. It writes JSON serialized files,
 accepts unicode keys, and tracks whether the store has been changed since last
 sync. It has no dependencies.
 
-JSON store is intended for smaller stores. Everything is kept in memory and
+json-store is intended for smaller stores. Everything is kept in memory and
 `sync()` writes the whole store to disk.
 
 For issues and development, see:

{json_store-4.4 → json_store-4.6}/README.md

@@ -1,14 +1,14 @@
-# JSON Store
+# json-store
 
 [![json-store](https://github.com/brainsik/json-store/actions/workflows/main.yml/badge.svg)](https://github.com/brainsik/json-store/actions/workflows/main.yml)
 ![PyPI](https://img.shields.io/pypi/v/json-store)
 ![PyPI - Python Version](https://img.shields.io/pypi/pyversions/json-store)
 
-JSON store is a simple replacement for shelve. It writes JSON serialized files,
+**json-store** is a simple replacement for shelve. It writes JSON serialized files,
 accepts unicode keys, and tracks whether the store has been changed since last
 sync. It has no dependencies.
 
-JSON store is intended for smaller stores. Everything is kept in memory and
+json-store is intended for smaller stores. Everything is kept in memory and
 `sync()` writes the whole store to disk.
 
 For issues and development, see:

{json_store-4.4 → json_store-4.6}/pyproject.toml

@@ -1,7 +1,7 @@
 [project]
 dynamic = ["version"]
 name = "json-store"
-requires-python = ">=3.10"
+requires-python = ">=3.11"
 dependencies = []
 
 authors = [{name = "jeremy avnet", email = "json-store@theory.org"}]
@@ -20,11 +20,11 @@ classifiers = [
 
     "Operating System :: OS Independent",
     "Programming Language :: Python :: 3",
-    "Programming Language :: Python :: 3.10",
     "Programming Language :: Python :: 3.11",
     "Programming Language :: Python :: 3.12",
     "Programming Language :: Python :: 3.13",
     "Programming Language :: Python :: 3.14",
+    "Programming Language :: Python :: 3.15",
     "Programming Language :: Python :: Implementation :: CPython",
     "Programming Language :: Python :: Implementation :: PyPy",
 ]
@@ -39,11 +39,19 @@ Changelog = "https://github.com/brainsik/json-store/releases"
 shelve2json = "json_store.shelve2json:main"
 
 [build-system]
-requires = ["hatchling"]
+requires = ["hatchling==1.32.4"]
 build-backend = "hatchling.build"
 
+[tool.hatch.build.targets.sdist]
+include = [
+    "/pyproject.toml",
+    "/LICENSE.txt",
+    "/src",
+    "/tests",
+]
+
 [tool.hatch.version]
 path = "src/json_store/__init__.py"
 
 [dependency-groups]
-dev = ["pytest >=8.3"]
+dev = ["pytest >=9.1"]

{json_store-4.4 → json_store-4.6}/src/json_store/__init__.py

@@ -1,5 +1,5 @@
 from .json_store import JSONStore
 
-__version__ = "4.4"
+__version__ = "4.6"
 
 open = JSONStore

{json_store-4.4 → json_store-4.6}/src/json_store/json_store.py

@@ -1,4 +1,3 @@
-# encoding: utf-8
 """A JSON store to use in place of shelve. Unicode keys, FTW!
 
 This is for small stores. Everything is in memory and sync() always writes

{json_store-4.4 → json_store-4.6}/src/json_store/shelve2json.py

@@ -1,7 +1,7 @@
 #! /usr/bin/env python
-# encoding: utf-8
 """Naïvely create a json_store file from a shelve DB."""
 
+import dbm
 import os
 import shelve
 import sys
@@ -11,7 +11,7 @@ import json_store
 
 def convert(oldfile: str):
     if not os.path.isfile(oldfile):
-        raise ValueError("No such file: {}".format(oldfile))
+        raise ValueError(f"No such file: {oldfile}")
 
     name = oldfile
     # remove extensions that are implicitly added by the underlying DBM module
@@ -29,12 +29,12 @@ def convert(oldfile: str):
 
 def main(argv=sys.argv):
     if len(argv) < 2:
-        print("Usage: {0[0]} <shelve_db>".format(argv))
+        print(f"Usage: {argv[0]} <shelve_db>")
         return 1
 
     try:
         convert(argv[1])
-    except Exception as e:
+    except (*dbm.error, TypeError, ValueError) as e:
         print(str(e), file=sys.stderr)
         return 1
     return 0

{json_store-4.4 → json_store-4.6}/tests/test_json_store.py

@@ -1,4 +1,3 @@
-# encoding: utf-8
 import json
 import os
 import platform
@@ -13,7 +12,7 @@ def get_new_store(json_kw=None, mode=None):
     # get a random filename to use
     with NamedTemporaryFile(prefix=__name__ + ".") as f:
         path = f.name
-    assert not os.path.exists(path), "Tempfile was not deleted: %s" % path
+    assert not os.path.exists(path), f"Tempfile was not deleted: {path}"
 
     kwargs = {}
 
@@ -151,7 +150,6 @@ def test_unchanged_store_doesnt_write_new_file():
     new_store.sync()
 
     store = json_store.open(new_store.path)
-    print("Test: ", store._needs_sync)
     try:
         inode1 = os.stat(store.path).st_ino
         assert not store.sync(), "File was written?"

json_store-4.4/.github/workflows/codeql.yml

@@ -1,40 +0,0 @@
-# For most projects, this workflow file will not need changing; you simply need
-# to commit it to your repository.
-#
-# You may wish to alter this file to override the set of languages analyzed,
-# or to provide custom queries or build logic.
-#
-name: "CodeQL"
-
-on:
-  push:
-    branches: ["main"]
-  pull_request:
-    # The branches below must be a subset of the branches above
-    branches: ["main"]
-  schedule:
-    - cron: "27 8 * * 0"
-
-jobs:
-  analyze:
-    name: Analyze
-    runs-on: ubuntu-latest
-    permissions:
-      actions: read
-      contents: read
-      security-events: write
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-
-      # Initializes the CodeQL tools for scanning.
-      - name: Initialize CodeQL
-        uses: github/codeql-action/init@v3
-        with:
-          languages: python
-          # Details on CodeQL's query packs refer to : https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs
-          queries: security-and-quality
-
-      - name: Perform CodeQL Analysis
-        uses: github/codeql-action/analyze@v3

json_store-4.4/.github/workflows/main.yml

@@ -1,85 +0,0 @@
-name: json-store
-on: [push, pull_request]
-
-jobs:
-  lint:
-    runs-on: ubuntu-latest
-
-    steps:
-      - uses: actions/checkout@v5
-
-      - name: Install uv
-        uses: astral-sh/setup-uv@v6
-        with:
-          version: "latest"
-
-      - name: pre-commit cache
-        uses: actions/cache@v4
-        with:
-          path: ~/.cache/pre-commit
-          key: ${{ runner.os }}-pre-commit-${{ hashFiles('.pre-commit-config.yaml') }}
-          restore-keys: |
-            ${{ runner.os }}-pre-commit-
-
-      - name: Run pre-commit tests
-        run: uv tool run pre-commit run -a
-
-  build:
-    runs-on: ubuntu-latest
-
-    steps:
-      - uses: actions/checkout@v5
-
-      - name: Install uv
-        uses: astral-sh/setup-uv@v6
-        with:
-          version: "latest"
-
-      - name: Build package
-        run: uv build
-
-      - name: Store build artifacts
-        uses: actions/upload-artifact@v4
-        with:
-          name: dist
-          path: dist
-
-  test:
-    needs: [lint, build]
-    strategy:
-      matrix:
-        os: [ubuntu-latest]
-        python-version: ["3.10", "3.11", "3.12", "3.13", "3.14", "pypy-3.11"]
-        include:
-          - os: windows-latest
-            python-version: "3.10"
-          - os: macos-latest
-            python-version: "3.10"
-          - os: windows-latest
-            python-version: "3.14"
-          - os: macos-latest
-            python-version: "3.14"
-    runs-on: ${{ matrix.os }}
-
-    steps:
-      - uses: actions/checkout@v5
-
-      - name: Install uv
-        uses: astral-sh/setup-uv@v6
-        with:
-          version: "latest"
-
-      - name: Set up Python ${{ matrix.python-version }}
-        uses: actions/setup-python@v6
-        with:
-          python-version: ${{ matrix.python-version }}
-
-      - name: Install ${{ github.job }} dependencies
-        run: |
-          uv sync
-
-      - name: Test with pytest
-        run: uv run pytest
-
-      - name: Test shelve2json
-        run: uv run sh tests/test_shelve2json.sh

json_store-4.4/.pre-commit-config.yaml

@@ -1,30 +0,0 @@
-repos:
-  - repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v6.0.0
-    hooks:
-      - id: check-ast
-      - id: check-merge-conflict
-      - id: check-yaml
-      - id: end-of-file-fixer
-      - id: trailing-whitespace
-
-  - repo: https://github.com/rhysd/actionlint
-    rev: v1.7.11
-    hooks:
-      - id: actionlint
-
-  - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.15.1
-    hooks:
-      - id: ruff-check
-      - id: ruff-format
-
-  - repo: https://github.com/rvben/rumdl-pre-commit
-    rev: v0.1.21
-    hooks:
-      - id: rumdl
-
-  - repo: https://github.com/abravalheri/validate-pyproject
-    rev: v0.25
-    hooks:
-      - id: validate-pyproject

json_store-4.4/CODE_OF_CONDUCT.md

@@ -1,133 +0,0 @@
-
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, caste, color, religion, or sexual
-identity and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the overall
-  community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or advances of
-  any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email address,
-  without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official email address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-[json-store@theory.org](mailto:json-store@theory.org).
-All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series of
-actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or permanent
-ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior, harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within the
-community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.1, available at
-[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
-
-Community Impact Guidelines were inspired by
-[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
-
-For answers to common questions about this code of conduct, see the FAQ at
-[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
-[https://www.contributor-covenant.org/translations][translations].
-
-[homepage]: https://www.contributor-covenant.org
-[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
-[Mozilla CoC]: https://github.com/mozilla/diversity
-[FAQ]: https://www.contributor-covenant.org/faq
-[translations]: https://www.contributor-covenant.org/translations

json_store-4.4/DEVELOPMENT.md

@@ -1,46 +0,0 @@
-# Development
-
-## Releasing a new version
-
-Documentation is the first step on the road to automation. 😊
-
-Follow these steps in order.
-
-### Create new build on GitHub
-
-1. Update `json-store/__init__.py` with new version.
-1. Tag the commit
-
-	```sh
-	git tag -s v3.2
-	```
-
-1. Push commit and push tag
-
-	```sh
-	git push --atomic origin main v3.2
-	```
-
-### Release on GitHub
-
-1. Download artifacts from [GitHub workflow](https://github.com/brainsik/json-store/actions/workflows/main.yml).
-This will create a `dist/` directory.
-1. Create release from tag and write notes
-1. Attach files in `/path/to/dist`
-1. Publish
-
-### Release on PyPI
-
-1. Upload artifacts
-
-	```sh
-	uvx twine upload /path/to/dist/*
-	```
-
-### Cleanup
-
-```sh
-rm -rf /path/to/dist
-git clean -Xd -n  # check for the unexpected
-git clean -Xd -f
-```