Project Direction

[nhairs]

Hi all,

Pending the PEP 541 Request, I wanted to gather community feedback on the direction of this project.

My current thoughts are:

Version 3.0.0

Goal: bring project into maintained state

• Move to pyproject.toml
• Ensure local development works (local linting, testing, building, etc)
• Ensure CI works (test all versions, run on PRs etc)
• Update supported python versions
  • drop 3.6 support
  • CPython 3.7-3.12 (ubuntu, win, mac)
  • Pypy 3.7-3.10 (ubuntu, win, mac)
• Bug fixes
  • Tests failing with Python 3.12 madzak/python-json-logger#185
    Update CI Python Versions #2
  • Mark JsonFormatter's __init__ to return None madzak/python-json-logger#173
    Set JsonFormatter.__init__ return type to None #4

Version 3.x

Goal: modernise package and include feature requests

• Existing feature requests from old repository
• ORJSON (and other?) encoders
  Split core functionality and support orjson and msgspec #9

Support Policy

Security support: any python version that makes up at least 5% of total downloads and within 2 years of EOL (currently 3.7+)

Bug fixes and new features: only currently maintained versions of python (currently 3.8+)

Maintainers

I'd like to look for 1-3 persons who are interested in helping maintain the project. These persons would also serve as a "backup" to prevent this repository from becoming unmaintained. If you'd like to be involved let me know

[juliangilbey]

Brilliant, thanks @nhairs! One small suggestion: please could you import the tags from the original project as well?

[nhairs]

Brilliant, thanks @nhairs! One small suggestion: please could you import the tags from the original project as well?

Good call @juliangilbey. All tags are now pushed (ranging from v0.1.2 - v2.0.7)

[juliangilbey]

One other thing; the CHANGELOG.md file should either be kept up to date as you're making these changes or retired.

[nhairs]

One other thing; the CHANGELOG.md file should either be kept up to date as you're making these changes or retired.

Another good pick-up - I didn't notice that that file was there 🤦. I've updated it and linked to it from the README.

[jdmoldenhauer]

@nhairs thank you so much for taking up the flag on this!

I looked at a few PEP 541 requests, and it seems like they tend to not get closed unless the previous owner does some work in pypi. Do you have any plans for If the previous owner remains unresponsive?

Thanks again for doing this work for the community.

[nhairs]

Thanks @jdmoldenhauer

I looked at a few PEP 541 requests, and it seems like they tend to not get closed unless the previous owner does some work in pypi. Do you have any plans for If the previous owner remains unresponsive?

I ended up talking very briefly about this on the PyPI discord. The TLDR is that they're aware that the current PyPI maintainers can't really look after the requests which is what is causing the large backlog; and that they in the process of hiring a dedicated person to handle these requests - applications close 1 May.

Although I expect it's probably going to be at least a few months before any action happens on the PEP 541 request I made, I'm working on the assumption that it will eventually happen. In the mean time I'm publishing built packages via the project releases which can be used directly as a work around.

[nhairs]

I've put together a PR showcasing a potential 4.x release. Any feedback would be appreciated 🙏

#9

[nhairs]

With:

• Split core functionality and support orjson and msgspec #9
• Add tests for common types #11
• Improve non-standard type encoding #12

I'm comfortable with where the project is going from a code point of view. If the PEP 541 request goes through I will look for maintainers then.

Before I close off this issue would there be any interest in an announcement mailing list for new versions etc? (similar to https://groups.google.com/g/dnspython-announce)