As I wrote in my above comment, and in the followup email I sent after the bug was locked, I got the graphs I needed for my paper after about 5 minutes playing

As I wrote in my above comment, and in the followup email I sent after the bug was locked, I got the graphs I needed for my paper after about 5 minutes playing with the axes. No StackOverflow needed. My problem wasn't "I need these particular graphs to look right", my problem was "Using this library in a seemingly reasonable way can silently produce corrupt/misleading results". That's a problem for all potential new users, and hence why I decided to invest a bunch of time in narrowing it down, report and pursue it. I also didn't call the software itself objectively wrong; only the decisions/execution trace which lead to the incorrect graphs: "this script doesn't set any axis labels or ticks: those decisions are made by matplotlib and/or seaborn, and are objectively wrong in this situation, regardless of the algorithmic details of how they have been arrived at." I wouldn't have minded if it were closed as unfixable or something, but it was instead mischaracterised: "This is, in my opinion, a legitimate issue worthy of acknowledging (even if such acknowledgement takes the form of a "won't fix" closure)." I wouldn't recommend Seaborn to anyone who wasn't prepared to manually cross-check all of the entries and statistics in the resulting plots.