Release 0.3?
See original GitHub issueLooks like there have been various bugfixes and improvements since the last release. Perhaps the most interesting one is the new distributed implementation of ndmeasure.label()
from @jni and @jakirkham (#94).
Is it time for a new release? I suppose you’ll want to bump straight to 0.3, since Python 2.7 has been dropped (#119).
Issue Analytics
- State:
- Created 4 years ago
- Comments:25 (11 by maintainers)
Top Results From Across the Web
Release 0.3 · GitHub
Open-Source Web UI for Apache Kafka Management. Contribute to provectus/kafka-ui development by creating an account on GitHub.
Read more >Spark Release 0.3
Spark 0.3 brings a variety of new features. You can download it for either Scala 2.9 or Scala 2.8. Scala 2.9 Support. This...
Read more >Fast Release Wrinkle-Reducing 0.3% Retinol Night Serum
Kiehl's Retinol Fast Release Wrinkle-Reducing Night Serum formulated with 0.3% pure retinol helps accelerate skin surface cell renewal to visibly improve ...
Read more >Fast Release Wrinkle-Reducing 0.3% Retinol Night Serum
Fast Release Wrinkle-Reducing 0.3% Retinol Night Serum · Retinol penetrates up to 15 surface layers deep · Accelerated skin surface cell renewal ...
Read more >6.7. Release 0.3.15 — Rubix 0.2.12 documentation
6.7. Release 0.3.15¶. Fixes and Features¶. Run scavenger thread in daemon mode to allow jvm to exit. This prevents Spark apps from getting...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Disagreement is welcome and encouraged!
I do agree with you about
imageio-ffmpeg
. It might be possible to get pims to shift that import into the video loader instead of the imageio sequence reader, which would remove our concern.I’m not so sure about
jpype
, I didn’t think it was that heavyweight? I’m not sure how it works though, I don’t think it bundles java but maybe expects to find java already on your system. I guessed based on eyeballing these filesize numbers vs comparable imageio numbersSounds good 🙂
Have submitted PR ( https://github.com/conda-forge/dask-image-feedstock/pull/4 ) to give you permissions on the feedstock.
Details about joining in this comment (at the bottom of the page).