5 ms·
What other packages have you seen abusing import side effects? Shopify is the first one I've seen, so I don't think it's quite as common as you are implying, b
by hn_acc_2 6y ago
What other packages have you seen abusing import side effects?
Shopify is the first one I've seen, so I don't think it's quite as common as you are implying, but I'm curious to know what other bad behavior you have found
- OJFord 6y agoNot GP but I've been bitten by plenty of first-party implicit side-effects, both intended (by not me not now) and not (by me or otherwise).
- mikepurvis 6y agoSometimes libraries do a switcheroo where they run interpreted code on startup to locate the "real" implementation in a shared object, and then load that and replace themselves with it. I'm not sure this is really idomatic, but here's an example of what it looks like from OpenCV: https://github.com/opencv/opencv/blob/master/modules/python/package/cv2/__init__.py https://github.com/opencv/opencv/blob/master/modules/python/...
- xeromal 6y agoLaunchDarkly does. It does some querying behind the scenes and added a significant delay to the coldstarts of our lambda apis
- edoceo 6y agoTheir PHP one had a similar shell_exec after-affect (c2017), caused some odd things in our logs but we backed away from that solution
- jbay808 6y agoSKiDL (circuit design library) does this to a very large extent... https://github.com/xesscorp/skidl https://github.com/xesscorp/skidl
- ilovetux 6y agoAn example in the standard library is the antigravity package. While it is an inside joke it still requires a HTTP transaction similar to the shopify package import.