JSONManipulator is a Python package to retrieve, add, delete, change and store objects in JSON files.

Overview

JSONManipulator

https://travis-ci.com/pandrey2003/JSONManipulator.svg?branch=master Coveralls CodeFactor Codacy Badge Updates Python 3 Documentation Status https://pepy.tech/badge/jsonmanipulator

JSONManipulator is a Python package to retrieve, add, delete, change and store objects in JSON files.

Installation

Use the package manager pip to install JSONManipulator.

pip install JSONManipulator

Usage

Firstly, you need to set up your initial JSON file.

from JSONManipulator import set_up

set_up(
    full_path="enter/full/path/to/your/file/here"
)

Functionality

As soon as you set up your file, you can use classes of the package:

  1. GetInformation (retrieve information about particular objects in the file).
  2. ChangeValue (change values of particular objects in the file).
  3. ChangeAllValues (change values of all objects in the file).
  4. DeleteObject (delete particular objects in the file).
  5. AddObject (add a new object to the file).
  6. AddKey (add a new key to each object in the file).

More detailed information about the usage of the package can be found in the examples and docs folders.

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

License

MIT

Comments
  • Update coverage to 7.0.0

    Update coverage to 7.0.0

    This PR updates coverage from 6.5.0 to 7.0.0.

    Changelog

    7.0.0

    --------------------------
    
    Nothing yet.
    
    
    .. _changes_7-0-0b1:
    

    7.0.0b1

    <changes_7-0-0b1_>`_.)
    
    - Changes to file pattern matching, which might require updating your
    configuration:
    
    - Previously, ``*`` would incorrectly match directory separators, making
     precise matching difficult.  This is now fixed, closing `issue 1407`_.
    
    - Now ``**`` matches any number of nested directories, including none.
    
    - Improvements to combining data files when using the
    :ref:`config_run_relative_files` setting:
    
    - During ``coverage combine``, relative file paths are implicitly combined
     without needing a ``[paths]`` configuration setting.  This also fixed
     `issue 991`_.
    
    - A ``[paths]`` setting like ``*/foo`` will now match ``foo/bar.py`` so that
     relative file paths can be combined more easily.
    
    - The setting is properly interpreted in more places, fixing `issue 1280`_.
    
    - Fixed environment variable expansion in pyproject.toml files.  It was overly
    broad, causing errors outside of coverage.py settings, as described in `issue
    1481`_ and `issue 1345`_.  This is now fixed, but in rare cases will require
    changing your pyproject.toml to quote non-string values that use environment
    substitution.
    
    - Fixed internal logic that prevented coverage.py from running on
    implementations other than CPython or PyPy (`issue 1474`_).
    
    .. _issue 991: https://github.com/nedbat/coveragepy/issues/991
    .. _issue 1280: https://github.com/nedbat/coveragepy/issues/1280
    .. _issue 1345: https://github.com/nedbat/coveragepy/issues/1345
    .. _issue 1407: https://github.com/nedbat/coveragepy/issues/1407
    .. _issue 1474: https://github.com/nedbat/coveragepy/issues/1474
    .. _issue 1481: https://github.com/nedbat/coveragepy/issues/1481
    
    
    .. _changes_6-5-0:
    

    6.6.0

    - Changes to file pattern matching, which might require updating your
    configuration:
    
    - Previously, ``*`` would incorrectly match directory separators, making
     precise matching difficult.  This is now fixed, closing `issue 1407`_.
    
    - Now ``**`` matches any number of nested directories, including none.
    
    - Improvements to combining data files when using the
    :ref:`config_run_relative_files` setting, which might require updating your
    configuration:
    
    - During ``coverage combine``, relative file paths are implicitly combined
     without needing a ``[paths]`` configuration setting.  This also fixed
     `issue 991`_.
    
    - A ``[paths]`` setting like ``*/foo`` will now match ``foo/bar.py`` so that
     relative file paths can be combined more easily.
    
    - The :ref:`config_run_relative_files` setting is properly interpreted in
     more places, fixing `issue 1280`_.
    
    - When remapping file paths with ``[paths]``, a path will be remapped only if
    the resulting path exists.  The documentation has long said the prefix had to
    exist, but it was never enforced.  This fixes `issue 608`_, improves `issue
    649`_, and closes `issue 757`_.
    
    - Reporting operations now implicitly use the ``[paths]`` setting to remap file
    paths within a single data file.  Combining multiple files still requires the
    ``coverage combine`` step, but this simplifies some single-file situations.
    Closes `issue 1212`_ and `issue 713`_.
    
    - The ``coverage report`` command now has a ``--format=`` option.  The original
    style is now ``--format=text``, and is the default.
    
    - Using ``--format=markdown`` will write the table in Markdown format, thanks
     to `Steve Oswald <pull 1479_>`_, closing `issue 1418`_.
    
    - Using ``--format=total`` will write a single total number to the
     output.  This can be useful for making badges or writing status updates.
    
    - Combining data files with ``coverage combine`` now hashes the data files to
    skip files that add no new information.  This can reduce the time needed.
    Many details affect the speed-up, but for coverage.py's own test suite,
    combining is about 40% faster. Closes `issue 1483`_.
    
    - When searching for completely un-executed files, coverage.py uses the
    presence of ``__init__.py`` files to determine which directories have source
    that could have been imported.  However, `implicit namespace packages`_ don't
    require ``__init__.py``.  A new setting ``[report]
    include_namespace_packages`` tells coverage.py to consider these directories
    during reporting.  Thanks to `Felix Horvat <pull 1387_>`_ for the
    contribution.  Closes `issue 1383`_ and `issue 1024`_.
    
    - Fixed environment variable expansion in pyproject.toml files.  It was overly
    broad, causing errors outside of coverage.py settings, as described in `issue
    1481`_ and `issue 1345`_.  This is now fixed, but in rare cases will require
    changing your pyproject.toml to quote non-string values that use environment
    substitution.
    
    - An empty file has a coverage total of 100%, but used to fail with
    ``--fail-under``.  This has been fixed, closing `issue 1470`_.
    
    - The text report table no longer writes out two separator lines if there are
    no files listed in the table.  One is plenty.
    
    - Fixed a mis-measurement of a strange use of wildcard alternatives in
    match/case statements, closing `issue 1421`_.
    
    - Fixed internal logic that prevented coverage.py from running on
    implementations other than CPython or PyPy (`issue 1474`_).
    
    - The deprecated ``[run] note`` setting has been completely removed.
    
    .. _implicit namespace packages: https://peps.python.org/pep-0420/
    .. _issue 608: https://github.com/nedbat/coveragepy/issues/608
    .. _issue 649: https://github.com/nedbat/coveragepy/issues/649
    .. _issue 713: https://github.com/nedbat/coveragepy/issues/713
    .. _issue 757: https://github.com/nedbat/coveragepy/issues/757
    .. _issue 991: https://github.com/nedbat/coveragepy/issues/991
    .. _issue 1024: https://github.com/nedbat/coveragepy/issues/1024
    .. _issue 1212: https://github.com/nedbat/coveragepy/issues/1212
    .. _issue 1280: https://github.com/nedbat/coveragepy/issues/1280
    .. _issue 1345: https://github.com/nedbat/coveragepy/issues/1345
    .. _issue 1383: https://github.com/nedbat/coveragepy/issues/1383
    .. _issue 1407: https://github.com/nedbat/coveragepy/issues/1407
    .. _issue 1418: https://github.com/nedbat/coveragepy/issues/1418
    .. _issue 1421: https://github.com/nedbat/coveragepy/issues/1421
    .. _issue 1470: https://github.com/nedbat/coveragepy/issues/1470
    .. _issue 1474: https://github.com/nedbat/coveragepy/issues/1474
    .. _issue 1481: https://github.com/nedbat/coveragepy/issues/1481
    .. _issue 1483: https://github.com/nedbat/coveragepy/issues/1483
    .. _pull 1387: https://github.com/nedbat/coveragepy/pull/1387
    .. _pull 1479: https://github.com/nedbat/coveragepy/pull/1479
    
    
    
    .. _changes_6-6-0b1:
    

    6.6.0b1

    ----------------------------
    
    Links
    • PyPI: https://pypi.org/project/coverage
    • Changelog: https://pyup.io/changelogs/coverage/
    • Repo: https://github.com/nedbat/coveragepy
    opened by pyup-bot 1
  • Update twine to 3.7.1

    Update twine to 3.7.1

    This PR updates twine from 3.7.0 to 3.7.1.

    The bot wasn't able to find a changelog for this release. Got an idea?

    Links
    • PyPI: https://pypi.org/project/twine
    • Docs: https://twine.readthedocs.io/
    opened by pyup-bot 1
  • Update sphinx to 6.0.0

    Update sphinx to 6.0.0

    This PR updates Sphinx from 5.3.0 to 6.0.0.

    Changelog

    6.0.0

    =====================================
    
    Dependencies
    ------------
    
    * 10468: Drop Python 3.6 support
    * 10470: Drop Python 3.7, Docutils 0.14, Docutils 0.15, Docutils 0.16, and
    Docutils 0.17 support. Patch by Adam Turner
    
    Incompatible changes
    --------------------
    
    * 7405: Removed the jQuery and underscore.js JavaScript frameworks.
    
    These frameworks are no longer be automatically injected into themes from
    Sphinx 6.0. If you develop a theme or extension that uses the
    ``jQuery``, ``$``, or ``$u`` global objects, you need to update your
    JavaScript to modern standards, or use the mitigation below.
    
    The first option is to use the sphinxcontrib.jquery_ extension, which has been
    developed by the Sphinx team and contributors. To use this, add
    ``sphinxcontrib.jquery`` to the ``extensions`` list in ``conf.py``, or call
    ``app.setup_extension("sphinxcontrib.jquery")`` if you develop a Sphinx theme
    or extension.
    
    The second option is to manually ensure that the frameworks are present.
    To re-add jQuery and underscore.js, you will need to copy ``jquery.js`` and
    ``underscore.js`` from `the Sphinx repository`_ to your ``static`` directory,
    and add the following to your ``layout.html``:
    
    .. code-block:: html+jinja
    
      {%- block scripts %}
          <script src="{{ pathto('_static/jquery.js', resource=True) }}"></script>
          <script src="{{ pathto('_static/underscore.js', resource=True) }}"></script>
          {{ super() }}
      {%- endblock %}
    
    .. _sphinxcontrib.jquery: https://github.com/sphinx-contrib/jquery/
    
    Patch by Adam Turner.
    * 10471, 10565: Removed deprecated APIs scheduled for removal in Sphinx 6.0. See
    :ref:`dev-deprecated-apis` for details. Patch by Adam Turner.
    * 10901: C Domain: Remove support for parsing pre-v3 style type directives and
    roles. Also remove associated configuration variables ``c_allow_pre_v3`` and
    ``c_warn_on_allowed_pre_v3``. Patch by Adam Turner.
    
    Features added
    --------------
    
    * 10924: LaTeX: adopt better looking defaults for tables and code-blocks.
    See :confval:`latex_table_style` and the ``pre_border-radius`` and
    ``pre_background-TeXcolor`` :ref:`additionalcss` for the former defaults
    and how to re-enact them if desired.
    
    Bugs fixed
    ----------
    
    * 10984: LaTeX: Document :confval:`latex_additional_files` behavior for files
    with ``.tex`` extension.
    
    Links
    • PyPI: https://pypi.org/project/sphinx
    • Changelog: https://pyup.io/changelogs/sphinx/
    opened by pyup-bot 0
  • Update tox to 4.1.1

    Update tox to 4.1.1

    This PR updates tox from 4.0.19 to 4.1.1.

    The bot wasn't able to find a changelog for this release. Got an idea?

    Links
    • PyPI: https://pypi.org/project/tox
    • Changelog: https://pyup.io/changelogs/tox/
    opened by pyup-bot 0
  • Update tox to 4.0.19

    Update tox to 4.0.19

    This PR updates tox from 4.0.18 to 4.0.19.

    The bot wasn't able to find a changelog for this release. Got an idea?

    Links
    • PyPI: https://pypi.org/project/tox
    • Changelog: https://pyup.io/changelogs/tox/
    opened by pyup-bot 0
  • Update tox to 4.0.18

    Update tox to 4.0.18

    This PR updates tox from 4.0.17 to 4.0.18.

    The bot wasn't able to find a changelog for this release. Got an idea?

    Links
    • PyPI: https://pypi.org/project/tox
    • Changelog: https://pyup.io/changelogs/tox/
    opened by pyup-bot 0
  • Update tox to 4.0.17

    Update tox to 4.0.17

    This PR updates tox from 4.0.16 to 4.0.17.

    The bot wasn't able to find a changelog for this release. Got an idea?

    Links
    • PyPI: https://pypi.org/project/tox
    • Changelog: https://pyup.io/changelogs/tox/
    opened by pyup-bot 0
  • Update coverage to 7.0.1

    Update coverage to 7.0.1

    This PR updates coverage from 6.5.0 to 7.0.1.

    Changelog

    7.0.1

    --------------------------
    
    - When checking if a file mapping resolved to a file that exists, we weren't
    considering files in .whl files.  This is now fixed, closing `issue 1511`_.
    
    - File pattern rules were too strict, forbidding plus signs and curly braces in
    directory and file names.  This is now fixed, closing `issue 1513`_.
    
    - Unusual Unicode or control characters in source files could prevent
    reporting.  This is now fixed, closing `issue 1512`_.
    
    - The PyPy wheel now installs on PyPy 3.7, 3.8, and 3.9, closing `issue 1510`_.
    
    .. _issue 1510: https://github.com/nedbat/coveragepy/issues/1510
    .. _issue 1511: https://github.com/nedbat/coveragepy/issues/1511
    .. _issue 1512: https://github.com/nedbat/coveragepy/issues/1512
    .. _issue 1513: https://github.com/nedbat/coveragepy/issues/1513
    
    
    .. _changes_7-0-0:
    

    7.0.0

    --------------------------
    
    Nothing new beyond 7.0.0b1.
    
    
    .. _changes_7-0-0b1:
    

    7.0.0b1

    <changes_7-0-0b1_>`_.)
    
    - Changes to file pattern matching, which might require updating your
    configuration:
    
    - Previously, ``*`` would incorrectly match directory separators, making
     precise matching difficult.  This is now fixed, closing `issue 1407`_.
    
    - Now ``**`` matches any number of nested directories, including none.
    
    - Improvements to combining data files when using the
    :ref:`config_run_relative_files` setting:
    
    - During ``coverage combine``, relative file paths are implicitly combined
     without needing a ``[paths]`` configuration setting.  This also fixed
     `issue 991`_.
    
    - A ``[paths]`` setting like ``*/foo`` will now match ``foo/bar.py`` so that
     relative file paths can be combined more easily.
    
    - The setting is properly interpreted in more places, fixing `issue 1280`_.
    
    - Fixed environment variable expansion in pyproject.toml files.  It was overly
    broad, causing errors outside of coverage.py settings, as described in `issue
    1481`_ and `issue 1345`_.  This is now fixed, but in rare cases will require
    changing your pyproject.toml to quote non-string values that use environment
    substitution.
    
    - Fixed internal logic that prevented coverage.py from running on
    implementations other than CPython or PyPy (`issue 1474`_).
    
    .. _issue 991: https://github.com/nedbat/coveragepy/issues/991
    .. _issue 1280: https://github.com/nedbat/coveragepy/issues/1280
    .. _issue 1345: https://github.com/nedbat/coveragepy/issues/1345
    .. _issue 1407: https://github.com/nedbat/coveragepy/issues/1407
    .. _issue 1474: https://github.com/nedbat/coveragepy/issues/1474
    .. _issue 1481: https://github.com/nedbat/coveragepy/issues/1481
    
    
    .. _changes_6-5-0:
    

    6.6.0

    - Changes to file pattern matching, which might require updating your
    configuration:
    
    - Previously, ``*`` would incorrectly match directory separators, making
     precise matching difficult.  This is now fixed, closing `issue 1407`_.
    
    - Now ``**`` matches any number of nested directories, including none.
    
    - Improvements to combining data files when using the
    :ref:`config_run_relative_files` setting, which might require updating your
    configuration:
    
    - During ``coverage combine``, relative file paths are implicitly combined
     without needing a ``[paths]`` configuration setting.  This also fixed
     `issue 991`_.
    
    - A ``[paths]`` setting like ``*/foo`` will now match ``foo/bar.py`` so that
     relative file paths can be combined more easily.
    
    - The :ref:`config_run_relative_files` setting is properly interpreted in
     more places, fixing `issue 1280`_.
    
    - When remapping file paths with ``[paths]``, a path will be remapped only if
    the resulting path exists.  The documentation has long said the prefix had to
    exist, but it was never enforced.  This fixes `issue 608`_, improves `issue
    649`_, and closes `issue 757`_.
    
    - Reporting operations now implicitly use the ``[paths]`` setting to remap file
    paths within a single data file.  Combining multiple files still requires the
    ``coverage combine`` step, but this simplifies some single-file situations.
    Closes `issue 1212`_ and `issue 713`_.
    
    - The ``coverage report`` command now has a ``--format=`` option.  The original
    style is now ``--format=text``, and is the default.
    
    - Using ``--format=markdown`` will write the table in Markdown format, thanks
     to `Steve Oswald <pull 1479_>`_, closing `issue 1418`_.
    
    - Using ``--format=total`` will write a single total number to the
     output.  This can be useful for making badges or writing status updates.
    
    - Combining data files with ``coverage combine`` now hashes the data files to
    skip files that add no new information.  This can reduce the time needed.
    Many details affect the speed-up, but for coverage.py's own test suite,
    combining is about 40% faster. Closes `issue 1483`_.
    
    - When searching for completely un-executed files, coverage.py uses the
    presence of ``__init__.py`` files to determine which directories have source
    that could have been imported.  However, `implicit namespace packages`_ don't
    require ``__init__.py``.  A new setting ``[report]
    include_namespace_packages`` tells coverage.py to consider these directories
    during reporting.  Thanks to `Felix Horvat <pull 1387_>`_ for the
    contribution.  Closes `issue 1383`_ and `issue 1024`_.
    
    - Fixed environment variable expansion in pyproject.toml files.  It was overly
    broad, causing errors outside of coverage.py settings, as described in `issue
    1481`_ and `issue 1345`_.  This is now fixed, but in rare cases will require
    changing your pyproject.toml to quote non-string values that use environment
    substitution.
    
    - An empty file has a coverage total of 100%, but used to fail with
    ``--fail-under``.  This has been fixed, closing `issue 1470`_.
    
    - The text report table no longer writes out two separator lines if there are
    no files listed in the table.  One is plenty.
    
    - Fixed a mis-measurement of a strange use of wildcard alternatives in
    match/case statements, closing `issue 1421`_.
    
    - Fixed internal logic that prevented coverage.py from running on
    implementations other than CPython or PyPy (`issue 1474`_).
    
    - The deprecated ``[run] note`` setting has been completely removed.
    
    .. _implicit namespace packages: https://peps.python.org/pep-0420/
    .. _issue 608: https://github.com/nedbat/coveragepy/issues/608
    .. _issue 649: https://github.com/nedbat/coveragepy/issues/649
    .. _issue 713: https://github.com/nedbat/coveragepy/issues/713
    .. _issue 757: https://github.com/nedbat/coveragepy/issues/757
    .. _issue 991: https://github.com/nedbat/coveragepy/issues/991
    .. _issue 1024: https://github.com/nedbat/coveragepy/issues/1024
    .. _issue 1212: https://github.com/nedbat/coveragepy/issues/1212
    .. _issue 1280: https://github.com/nedbat/coveragepy/issues/1280
    .. _issue 1345: https://github.com/nedbat/coveragepy/issues/1345
    .. _issue 1383: https://github.com/nedbat/coveragepy/issues/1383
    .. _issue 1407: https://github.com/nedbat/coveragepy/issues/1407
    .. _issue 1418: https://github.com/nedbat/coveragepy/issues/1418
    .. _issue 1421: https://github.com/nedbat/coveragepy/issues/1421
    .. _issue 1470: https://github.com/nedbat/coveragepy/issues/1470
    .. _issue 1474: https://github.com/nedbat/coveragepy/issues/1474
    .. _issue 1481: https://github.com/nedbat/coveragepy/issues/1481
    .. _issue 1483: https://github.com/nedbat/coveragepy/issues/1483
    .. _pull 1387: https://github.com/nedbat/coveragepy/pull/1387
    .. _pull 1479: https://github.com/nedbat/coveragepy/pull/1479
    
    
    
    .. _changes_6-6-0b1:
    

    6.6.0b1

    ----------------------------
    
    Links
    • PyPI: https://pypi.org/project/coverage
    • Changelog: https://pyup.io/changelogs/coverage/
    • Repo: https://github.com/nedbat/coveragepy
    opened by pyup-bot 0
  • Update tox to 4.0.16

    Update tox to 4.0.16

    This PR updates tox from 4.0.15 to 4.0.16.

    The bot wasn't able to find a changelog for this release. Got an idea?

    Links
    • PyPI: https://pypi.org/project/tox
    • Changelog: https://pyup.io/changelogs/tox/
    opened by pyup-bot 0
  • Update tox to 4.0.15

    Update tox to 4.0.15

    This PR updates tox from 4.0.14 to 4.0.15.

    The bot wasn't able to find a changelog for this release. Got an idea?

    Links
    • PyPI: https://pypi.org/project/tox
    • Changelog: https://pyup.io/changelogs/tox/
    opened by pyup-bot 0
  • Update tox to 4.0.14

    Update tox to 4.0.14

    This PR updates tox from 4.0.12 to 4.0.14.

    The bot wasn't able to find a changelog for this release. Got an idea?

    Links
    • PyPI: https://pypi.org/project/tox
    • Changelog: https://pyup.io/changelogs/tox/
    opened by pyup-bot 0
  • Help Wanted

    Help Wanted

    JSONManipulator is a popular library that can teach any developer interacting with it the principles of OOP. Currently, I do not have enough time to maintain/refactor it, however, the code complexity in some places is monstrous and the approaches are not always clean.

    In case you have a vision of how you can apply good design principles to this code, feel free to submit a pull request. I will be more than happy to add you as a contributor to a project.

    help wanted 
    opened by pandrey2003 0
Releases(v.3.1.1)
A fast streaming JSON parser for Python that generates SAX-like events using yajl

json-streamer jsonstreamer provides a SAX-like push parser via the JSONStreamer class and a 'object' parser via the ObjectStreamer class which emits t

Kashif Razzaqui 196 Dec 15, 2022
json|dict to python object

Pyonize convert json|dict to python object Setup pip install pyonize Examples from pyonize import pyonize

bilal alpaslan 45 Nov 25, 2022
Convert Wii UI formats to JSON5 and vice versa

Convert Wii UI formats to JSON5 and vice versa

Pablo Stebler 11 Aug 28, 2022
JsonParser - Parsing the Json file by provide the node name

Json Parser This project is based on Parsing the json and dumping it to CSV via

Ananta R. Pant 3 Aug 08, 2022
Same as json.dumps or json.loads, feapson support feapson.dumps and feapson.loads

Same as json.dumps or json.loads, feapson support feapson.dumps and feapson.loads

boris 5 Dec 01, 2021
MOSP is a platform for creating, editing and sharing validated JSON objects of any type.

MONARC Objects Sharing Platform Presentation MOSP is a platform for creating, editing and sharing validated JSON objects of any type. You can use any

CASES Luxembourg 72 Dec 14, 2022
A Cobalt Strike Scanner that retrieves detected Team Server beacons into a JSON object

melting-cobalt 👀 A tool to hunt/mine for Cobalt Strike beacons and "reduce" their beacon configuration for later indexing. Hunts can either be expans

Splunk GitHub 150 Nov 23, 2022
With the help of json txt you can use your txt file as a json file in a very simple way

json txt With the help of json txt you can use your txt file as a json file in a very simple way Dependencies re filemod pip install filemod Installat

Kshitij 1 Dec 14, 2022
Simple Python Library to convert JSON to XML

json2xml Simple Python Library to convert JSON to XML

Vinit Kumar 79 Nov 11, 2022
Python script for converting .json to .md files using Mako templates.

Install Just install poetry and update script dependencies Usage Put your settings in settings.py and .json data (optionally, with attachments) in dat

Alexey Borontov 6 Dec 07, 2021
Fileson - JSON File database tools

Fileson is a set of Python scripts to create JSON file databases

Joonas Pihlajamaa 2 Feb 02, 2022
JSONManipulator is a Python package to retrieve, add, delete, change and store objects in JSON files.

JSONManipulator JSONManipulator is a Python package to retrieve, add, delete, change and store objects in JSON files. Installation Use the package man

Andrew Polukhin 1 Jan 07, 2022
Console to handle object storage using JSON serialization and deserealization.

Console to handle object storage using JSON serialization and deserealization. This is a team project to develop a Python3 console that emulates the AirBnb object management.

Ronald Alexander 3 Dec 03, 2022
Convert your subscriptions csv file into a valid json for Newpipe!

Newpipe-CSV-Fixer Convert your Google subscriptions CSV file into a valid JSON for Newpipe! Thanks to nikcorg for sharing how to convert the CSV into

Juanjo 44 Dec 29, 2022
Simple, minimal conversion of Bus Open Data Service SIRI-VM data to JSON

Simple, minimal conversion of Bus Open Data Service SIRI-VM data to JSON

Andy Middleton 0 Jan 22, 2022
This open source Python project allow you to create JSON data trees using Minmup.com

This open source Python project allow you to create JSON data trees using Minmup.com. I try to develop this project all the time. But feel free to use :).

Arttu Väisänen 1 Jan 30, 2022
A JSON utility library for Python featuring Django-style queries and mutations.

JSON Enhanced JSON Enhanced implements fast and pythonic queries and mutations for JSON objects. Installation You can install json-enhanced with pip:

Collisio Technologies 4 Aug 22, 2022
simdjson : Parsing gigabytes of JSON per second

JSON is everywhere on the Internet. Servers spend a *lot* of time parsing it. We need a fresh approach. The simdjson library uses commonly available SIMD instructions and microparallel algorithms to

16.3k Dec 29, 2022
Wikidot-forum-dump - Simple Python script that dumps a Wikidot wiki forum into JSON structures.

wikidot-forum-dump Script is partially based on 2stacks by bluesoul: https://github.com/scuttle/2stacks To dump a Wiki's forum, edit config.py and put

ZZYZX 1 Jun 29, 2022
A fast JSON parser/generator for C++ with both SAX/DOM style API

A fast JSON parser/generator for C++ with both SAX/DOM style API Tencent is pleased to support the open source community by making RapidJSON available

Tencent 12.6k Dec 30, 2022