Replying to
@Tutanota@mastodon.social what does this mean? How can it pass with only a minority voting in favour???
Remote
Juan Nunez-Iglesias
@jni@fosstodon.org
mastodon 4.7.3Core dev and co-founder napari.org
Core dev scikit-image.org
Co-author elegant-scipy.org
Research Fellow at https://www.monash.edu/researchinfrastructure/eresearch
542 Followers
387 Following
22 Posts
Joined November 20, 2022
GitHub:
Twitter:
RE: @briankrebs@infosec.exchange
“Important AWS Tokens.txt”
RE: @petersuber@fediscience.org
I’ve been reading a lot about cooperatives over the past year for image.coop, and am totally convinced that all universities should change to a cooperative governance model.
Amazing new #Python #PEP to improve optional dependencies handling:
https://peps.python.org/pep-0771/
The PEP is very thorough and well-written, and it perfectly uses @napari@fosstodon.org as a motivating example. We were not involved but we fully endorse it! 😃
Replying to
@simon one reason the axios blast radius was so big is uvx’s big cousin, npx, which could execute downstream tools that depended on unpinned axios. I feel like we should not recommend uvx/npx until they have cooldown periods by default.
Replying to
@saucoide @brettcannon based on other conversations I'm having, it seems the tooling hasn't quite caught up with the standard…
Replying to
@brettcannon One thing I'm not clear on: we don't use lock files for "library" use, ie if you pip install napari, you get whatever new version of the dependencies is up there. So this wouldn't help in that scenario, right? Is your assertion that it would have helped people catch on faster, or that we should all be locking our dependencies? (Which I think is generally an antipattern in Python as it leads to mutually incompatible libraries...?)
Replying to
@steve “I just wish they'd used a pre-industrial average as the baseline.”
👆This! Humans have short memories, but why should we institutionalise this with our data vis??? 🤦♂️
Replying to
@steveroyle@biologists.social can you expand on "make a static archive"? (I also want this to be publicly visible.)
Replying to
@albertcardona@mathstodon.xyz @jonny@neuromatch.social yeah, most aren’t. But I unfortunately got in the habit of using Twitter as my demo/ announcement space. When performance reviews came around I would check my tweets for the past year 😂. I’d like a nice UI to look at those again. Some manual culling would be warranted, indeed.
Replying to
@kristinmbranson@social.coop @steveroyle@biologists.social I also never gelled with Zotero *until* the recent v7 release, which is a dramatic improvement! So, worth giving it another shot I think!
Replying to
@kisharrington ask @czaki. But iirc he said it would be super hard (I presume it’s a Qt issue)
Replying to
@eeeps@front-end.social very fun read! This caught my eye:
Worse, the more experiments people did, the clearer it became that no three-dimensional space could ever be perceptually uniform
That reminded me of this paper showing that 3D rotations cannot be represented in a continuous 3D space (because 360º wraps to 0), but can be represented in a continuous 5D space. Wouldn't it be excellent if there was a higher-dimensional space out there that captured perceptual uniformity? 🤯
Replying to
@jonny@neuromatch.social you’re probably focused on the future but I wonder if you have ideas here… 👆
Replying to
@brettcannon @pjacock @dangoodin do you have a human- (read: noob-) readable intro to these concepts? I don’t think we use pylock in any of the projects I lead. 😬
Replying to
Replying to
@almar @brettcannon "using a lockfile only for CI" We do this for napari! But we use requirements.txt based constraints, not pylock.toml, so when a version is updated, we kinda just bump it. 😅 (Once a week.) It does mean in most cases we have a built-in cooldown period.
But yes, this doesn't really help end users. I think the best thing for users is that uv/pip etc should have cooldown periods by default, and a --unsafe-get-absolute-latest opt-in flag for getting "today's" release.
@albertcardona@mathstodon.xyz I recall that a long time ago (almost certainly on the other site) you shared an rsync incantation for efficiently and robustly moving large directories of files (ie ome-zarr volumes) within a single machine or over the network. Ringing any bells?