3 ms·
Many congrats on the release & also thanks to the Scrapy team for the effort involved. As far as I am concerned, this was the last package I used heavily that
by djm_ 11y ago
Many congrats on the release & also thanks to the Scrapy team for the effort involved.
As far as I am concerned, this was the last package I used heavily that still had not made the upgrade.
For the Python community: which packages are you still waiting for/working on?
- vially 11y agoI've been waiting for Fabric to make the migration to Python 3. Fortunately I no longer use Python that much (I jumped on the hype train to Go and I've been very satisfied with it) so I no longer need Fabric nowadays.
- crdoconnor 11y agoMechanize would be nice, but it's practically abandonware at this point.
- kevinwang 11y agosame
- random_upvoter 11y agoA wrapper for the exiv2 library (for editing metadata of picture files) that works on Windows
- xemoka 11y agoEsri's ArcPy module and ArcGIS Desktop's "built-in" python environment. :( ArcGIS Pro is using 3.4, so the wrappers for ArcObjects are updated, but who knows if they will put that work back into ArcGIS Desktop...
- craigds 11y agoStill waiting on Ansible to make the jump. As far as I can tell it's not even on their roadmap, which is a bit crazy given that _almost_ everyone else has solved this by now. This may not be a blocker for the rest of our stuff though, since ansible can install its own python 2 on servers automatically.