Login

Recent searches

No recent searches

Search options

Only available when logged in.
social.coop is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Fediverse instance for people interested in cooperative and collective projects. If you are interested in joining our community, please apply at https://join.social.coop/registration-form.html.

Administered by:

Server stats:

492
active users

social.coop: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.4

Public *
leah wasser

Tips to prevent maintainer burnout from the beautiful soup maintainer. A single maintainer managing a package will millions of users

*ask users to contribute issues before a pr
* practice defensive programming. Use warnings to point to common user mistakes

Slide showing a list of bullet points associated with maintainer burnout and the beautiful soup maintainer standing at a podium . My boundaries after twenty years I probably won’t respond to your support request - (Unless it looks like you hit a bug.) I practice defensive coding (especially using `warnings.warn`) - Provides automatic support for common mistakes Courtesy is even more important than usual I’m *interested* in the quality of my dependencies (lxml et al) - I’ll file bugs but won’t try to fix them I’m *committed* to the quality of the beautifulsoup4 package - If I walk away or die, the current release should work for a long time. I practice software hygiene (unit tests, type hints) - Gives me confidence that I can come back after a break Bug reports > pull requests
#pyconus#python#opensource
Public
Sumana Harihareswara

@leahawasser

The text from @leonardr 's slide:

My boundaries after twenty years

I probably won’t respond to your support request
- (Unless it looks like you hit a bug.)

I practice defensive coding (especially using `warnings.warn`)
- Provides automatic support for common mistakes

I practice software hygiene (unit tests, type hints)
- Gives me confidence that I can come back after a break

Bug reports > pull requests

[1/2]

Sumana Harihareswara

@leahawasser

Courtesy is even more important than usual

I’m *interested* in the quality of my dependencies (lxml et al)
- I’ll file bugs but won’t try to fix them

I’m *committed* to the quality of the beautifulsoup4 package
- If I walk away or die, the current release should work for a long time.

@leonardr

[2/2]

May 18, 2024, 08:34 AM·Public
0boosts·1favorite
ExploreLive feeds
About