Beni Cherniavsky-Paskin

Yeah. You need to create a `Kubeclient::Client` per API group you use. I don't see this changing soon. The way Kubeclient creates methods per resource, like `get_deployments`, ties a client...

Now that we have `as: :parsed_symbolized` and `as: :parsed` (#306), kubeclient `get_foo` may give you data that isn't a `Kubeclient::Resource`, and in the latter case that you can't write back...

hmm, good idea.

Unlikely that o be addressed, but valid. @miq-bot remove-label stale

I started using toolbox 0.0.99.5 today on fedora 38 (NOT silverblue, I'm just while following some tuturial that didn't want to mess up my host), and was mystified how toolbox...

If a package uses a concrete list like `python_version = "3.5,3.6,3.7,3.8"`, it will be a problem for consumers as existing code most probably works in next python version e.g. 3.9...

Interestingly, markers qualifying _whether a dependency is required_ already support complex python_version conditions, e.g. example now in README: ``` unittest2 = {version = ">=1.0,= '3.0' and python_version < '3.4')"} ```

Cocalc (formerly SageMathCloud) is open source (though a large beast to self host) and has a collaborative LaTeX editor: http://blog.sagemath.com/latex/2017/02/06/smc-for-latex.html

Never done it myself. https://github.com/sagemathinc/cocalc#very-easy-install-of-cocalc-on-your-computer says easiest is to run in docker: https://github.com/sagemathinc/cocalc-docker (note security status there, it's not quite for untrusted users).

This updates the code to match [documented](https://pymongo.readthedocs.io/en/3.13.0/api/pymongo/collection.html#pymongo.collection.Collection.find) functionality for `pymongo==3.13.0` currently in requirements.txt. The dependency has already been bumped in commit 8406b3189797a5b14059ce5dc8ffe2e12b4e9f28 and I'm pretty convinced these code paths have...