Skip to content

Low level APIs #10

@jonathanfine

Description

@jonathanfine

I think we need two low-level APIs.

  1. The legacy API, which is the current API ported to Python 3.
  2. A properly documented and tested replacement to the legacy API.

The only changes I'd like to make with the legacy API are those that support compatibility with legacy code. I think 2to3 has already made all those changes.

I'd like the replacement low-level API to be

  • Conceptually simple.
  • Small.
  • Stable
  • Easy to test.

I've done some experiments, and it seems that sending bad API requests to Minecraft can cause to freeze. We don't want that to happen, and we want to be able to reproduce this fault when it does.

So I'd also like the replacement API to provide

  • Safety - does not crash or freeze Minecraft
  • Logging - to diagnose problems when then do occur

Logging will also help with testing and debugging the high-level API.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions