MattsFace

Hey guys,

I've been at QFC for six months now. It's my first retail experience and it has slowly turned into the worst job I've ever had. Especially on labor day. We were so understaffed in the front end (again) it's like they didn't even schedule more people for the holiday. At one point we had one special needs cashier clerk who bless his heart can't bag.. My line was going more than half way down the freezer isle and I did my union duty and didn't check any faster..

Kroger's hiring/staffing/retention policies are going to drive this place into the ground. We don't even enforce the attendance policy at my store. Everyone just calls out or shows up late all the time.

This was my first un

I’m getting ready to release python-mlb-statsapi 1.1.0.

The big update is async support with AsyncMlb and AsyncMlbDataAdapter, while keeping the existing sync API working the same way for current users.

I also did a pretty big README refactor so the project is easier to understand and get started with.

This ended up being a much bigger project than just swapping requests for HTTPX. A lot of the work was making sure sync and async actually behave the same and don’t introduce weird lifecycle or client ownership issues.

The final PR is up and I’m pretty happy with where it landed. I just need to run a couple live MLB API tests before I merge it.

Repo:
https://github.com/zero-sum-seattle/

I’m getting ready to release python-mlb-statsapi 1.1.0.

The big update is async support with AsyncMlb and AsyncMlbDataAdapter, while keeping the existing sync API working the same way for current users.

I also did a pretty big README refactor so the project is easier to understand and get started with.

This ended up being a much bigger project than just swapping requests for HTTPX. A lot of the work was making sure sync and async actually behave the same and don’t introduce weird lifecycle or client ownership issues.

The final PR is up and I’m pretty happy with where it landed. I just need to run a couple live MLB API tests before I merge it.

Repo:
https://github.com/zero-sum-seattle/

Hey guys I maintain python-mlb-statsapi, a Python wrapper for the MLB Stats API, and I’m working on v1.1.0.

The biggest addition is first-class async support with AsyncMlb. I’m also updating and cleaning up the README/docs so the project is easier to understand and use.
Before I release it, I’d really appreciate some outside eyes on it.

There is no ego here. If something about the API feels weird, the async design looks wrong, the docs are confusing, the tests seem excessive, or there’s something I’m overengineering, I want to hear it.

Honestly I’d love to talk about retry logic. I want to make something that works well for us.

I’ve got a real cool project that uses my module coming to

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

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

I finally pushed v1.0.0 of python-mlb-statsapi.

This release finishes up the HTTP work I started in 0.8 and 0.9 and gives the library a stable public API contract going forward.

The biggest breaking change:

Mlb() now uses strict HTTP handling by default.

In 0.9, strict mode was optional:

mlb = mlbstatsapi.Mlb(strict_http=True)

In 1.0, this is now the default:

mlb = mlbstatsapi.Mlb()

Final non-404 4xx responses now raise MlbHttpError instead of silently returning the historical empty result.

404 behavior is intentionally unchanged. Depending on the endpoint, a 404 can still return None, [], or {}.

If you aren’t ready to migrate yet, the old 0.9 behavior is still available explici

I finally pushed v1.0.0 of python-mlb-statsapi.

This release finishes up the HTTP work I started in 0.8 and 0.9 and gives the library a stable public API contract going forward.

The biggest breaking change:

Mlb() now uses strict HTTP handling by default.

In 0.9, strict mode was optional:

mlb = mlbstatsapi.Mlb(strict_http=True)

In 1.0, this is now the default:

mlb = mlbstatsapi.Mlb()

Final non-404 4xx responses now raise MlbHttpError instead of silently returning the historical empty result.

404 behavior is intentionally unchanged. Depending on the endpoint, a 404 can still return None, [], or {}.

If you aren’t ready to migrate yet, the old 0.9 behavior is still available explici

Hey guys,

40 year old straight male here. My 30s were a rough time. I was hopelessly self medicating with Benzodiazepines and alcohol due to the stress of a career. I lost a good relationship because of it.

Without giving you guys a whole story about my past I've been on a long journey the past six years. I checked my self into treatment and got clean all of that substance abuse. I don't have a solid six years of sobriety under my belt, but I'm getting so much more consistent and if / when a relapse happens (it's only been booze at this point). I catch my self and pull my self right out of it. Then I meet with my medical professional to go over what occurred and also go into some deep s

I’ve been working on version 0.9.0 of my Python MLB Stats API wrapper, and the final release PR is ready for review.

I’ll go through the code again after I finish my shit cashiering shift today. I miss working tech…

Anyway,

This release adds a public retry policy, richer HTTP errors, an optional strict mode, compatibility warnings, and a versioned User-Agent while keeping the existing return behavior as the default.

It also starts preparing users for a possible breaking change in 1.0.0. Right now most non-404 4xx responses return an empty result for compatibility. In 1.0.0, strict HTTP handling may become the default, meaning those responses would raise an actual exception instead.

The

I’ve been working on version 0.9.0 of my Python MLB Stats API wrapper, and the final release PR is ready for review.

I’ll go through the code again after I finish my shit cashiering shift today. I miss working tech…

Anyway,

This release adds a public retry policy, richer HTTP errors, an optional strict mode, compatibility warnings, and a versioned User-Agent while keeping the existing return behavior as the default.

It also starts preparing users for a possible breaking change in 1.0.0. Right now most non-404 4xx responses return an empty result for compatibility. In 1.0.0, strict HTTP handling may become the default, meaning those responses would raise an actual exception instead.

The