This isn't a PyCon problem at all. By all accounts, the staff and management of PyCon did everything correctly and by the book. It was an *attendee* problem.
Should the jokes have been made? No. Should someone have said something? Yes. Should PyCon staff have been alerted? Should a picture have been taken, published to the public internet? No. Should anyone have been fired? No. Should this have been handled privately? Yes.
I'd never heard of any of the parties involved until 2-3 days ago. But I agree that we all lost. And if the reported interactions in there are true (and, honestly, I can't see why someone would fabricate that when it's so easily verifiable), then the first party seems to have a history of *not* dealing with things with the people in question, but instead screaming to the rest of the world to incite massive action. It just seems to have eventually backfired this time.
Frankly, I don't care either way. I don't think the word "dongle" was ever even uttered in my workplace until this week. Forking was, but that's what happens with developers and public repos. If I were a Python developer, I'd consider going to PyCon. Just like if I were an active Ruby developer, I'd consider RubyCon despite similar issues in the past. I think I recall a PHP one, too. It's not the con, the organizers, or the sponsors who are to be blamed for these things, especially when they have publish codes of conduct.