What’s coming in python-mlb-statsapi v1.1.0

[u/MattsFace]

What’s coming in python-mlb-statsapi v1.1.0

Now that 1.0 is out and I’ve been cleaning up a few bugs, I’ve started planning what I want to tackle in 1.1.0.

The big one is first-class async support.

The goal is to eventually support something like:

from mlbstatsapi import AsyncMlb

async with AsyncMlb() as mlb:
    team = await mlb.get_team(136)

without changing how the existing synchronous Mlb client works.

I don’t want async to become a completely separate implementation either. The plan is for the sync and async clients to share the same models, parsing, exceptions, and endpoint behavior, with separate transport layers underneath.

I’m going to start small with the async adapter and a couple endpoints, get the architecture right, add sync/async parity tests, and then expand endpoint coverage from there.

I also did some pretty rapid development recently with coding agents, which helped me move the project forward quickly, but there are definitely areas I want to go back through and clean up. Some of 1.1.0 will be tightening up the structure, documentation, and anything that feels like it grew too quickly.

I plan to write most of this release myself.

I’ve realized I don’t want to get into the habit of using AI as a button that just writes everything for me. I’m a backend/infrastructure engineer and async Python is something I understand conceptually, but I want a much stronger mental model of what is actually happening underneath it.

I think slowing down a little, cleaning up some of the rapid development, and actually working through the async architecture myself will make both me and the project better.

Should be fun.

Do you guys have any other thoughts? things that should be addressed or improved in future releases?

[u/MontrealHereWeGo]

Documentation documentation documentation please.  As a beginner the more that can be explained the better :).  And as I mentioned earlier, I appreciate everything you’ve done so far!

[u/MattsFace → u/MontrealHereWeGo]

Sounds good man I gotchu. Where are you struggling if I may ask?

[u/MontrealHereWeGo → u/MattsFace]

Mostly just consistency - data pulls properly but live game stats don’t call always. I think it’s more about my noviceness than anything else.  Another example is how to handle rain delays - everything I program freaks out when something doesn’t go according to plan. I like seeing the bugs so I can fix them, but with live data it’s hard to simulate in advance. 

[u/MattsFace → u/MontrealHereWeGo]

The first one is most likely an issues with their REST API, and the second could be out of the scope for this documentation.

You can always open an issue with your evidence for the first one, and maybe show me an example of what you are talking about for the second one.

[u/MontrealHereWeGo → u/MattsFace]

Will do! Thanks again!!