Hi folks, With the advent of the ytdata frontend, it seems that all usages of the GeometryHandler / Index object's functions save_data, _reload_data_file, load_object and get_data are all dead now. Any reason they can't be dispensed with? I suspect-without-evidence that even before ytdata, usage was close to nil. -Matt
Yes please rip out pickling support for data objects in yt-4, there’s an
awful lot of code to support it for very little utility.
On Tue, Jul 2, 2019 at 4:55 PM Matthew Turk
Hi folks,
With the advent of the ytdata frontend, it seems that all usages of the GeometryHandler / Index object's functions save_data, _reload_data_file, load_object and get_data are all dead now.
Any reason they can't be dispensed with? I suspect-without-evidence that even before ytdata, usage was close to nil.
-Matt _______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
I agree. I think it makes sense to cull the overlapping features that
aren't being used and/or maintained.
On Tue, Jul 2, 2019 at 10:12 PM Nathan
Yes please rip out pickling support for data objects in yt-4, there’s an awful lot of code to support it for very little utility.
On Tue, Jul 2, 2019 at 4:55 PM Matthew Turk
wrote: Hi folks,
With the advent of the ytdata frontend, it seems that all usages of the GeometryHandler / Index object's functions save_data, _reload_data_file, load_object and get_data are all dead now.
Any reason they can't be dispensed with? I suspect-without-evidence that even before ytdata, usage was close to nil.
-Matt _______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
participants (3)
-
Britton Smith
-
Matthew Turk
-
Nathan