merged

• Files Changed
• Browse Source

- update to 3.2.2 
  - Fixed compilation and async support of the yajl2_c backend in
    pyhthon 3.12 (#98).
  - Check IJSON_BUILD_YAJL2C environment variable when building
    ijson to force/skip building the yajl2_c backend (#102).
- changes from 3.2.1
  - Added support for Python 3.12.
  - Fixed a memory leak in the yajl2_c backend triggered only when
    the underlying yajl functions reported a failure (#97).
- changes from 3.2.0.post0
  - Fixed minor README rendering issues that prevented upload of
    3.2.0 distributions to PyPI.
- changes from 3.2.0
  - New ijson.dump command-line utility for simple inspection of
    the ijson iteration process. This tool should be useful for new
    users who are usually confused with how to use the library, and
    the prefix in particular.
  - Fixed bug in yajl2_c backend introduced in 3.1.2 where random
    crashes could occur due to an unsafe reference decrement when
    constructing the parse/items/kvitems generators (#66).
  - Mark Python 3.10 and 3.11 as explicitly supported.  
- drop the tests_asyncio.py

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

fix tests

• Files Changed
• Browse Source

- update to 3.1.4 
  * Fixed bug in ``yajl2_c`` backend introduced in 3.1.0
    where ``ijson.items`` didn't work correctly
    against member names containing ``.`` (#41).
  * Python backend raises errors on incomplete JSON content
    that previously wasn't recognised as such,
    aligning itself with the rest of the backends (#42).
  
  Contains 3.1.3:
  
  * Python backed correctly raises errors
    when JSON numbers with leading zeros
    are found in the stream (#40).
  * Likewise, JSON numbers with fractions
    where the decimal point is not surrounded
    by at least one digit on both sides
    also produce an error now
    on the python backend.
  * Fixed detection of file objects
    with generator-based ``read`` coroutines
    (i.e., a ``read`` generator decorated with ``@types.coroutine``)
    for the purpose of automatically routing user calls
    done through the main entry points.
    For example, when using ``aiofiles`` objects
    users could invoke ``async for item in ijson.parse_async(f)``
    but not ``async for item in ijson.parse(f)``,
    while the latter has been possible since 3.1
    for native coroutines.
  
  Contains 3.1.2.post0:

• Files Changed
• Browse Source

• Browse Source