[GitHub] anirudhacharya commented on issue #9686: APIs that might be a good idea to break in 2.0

[GitBox <gi...@apache.org>]

anirudhacharya commented on issue #9686: APIs that might be a good idea to break in 2.0
URL: https://github.com/apache/incubator-mxnet/issues/9686#issuecomment-430800656
 
 
   Taking a brief look at [Data Iterators](http://mxnet.incubator.apache.org/api/python/io/io.html#data-iterators), it would seem the iterators are split up between the  mx.io  module and mx.image module. And there does not seem to be any method/process( correct me if I am wrong) in the split. For instance,
   - ImageRecordIter and ImageRecordUInst8Iter( along with CSVIter, NDArrayIter, LibSVMIter) are under mx.io
   - whereas ImageIter and ImageDetIter are under mx.image module
   
   And 
   
   - There are image processing functions like imdecode, scale_down, resize_short etc.. under mx.image here - http://mxnet.incubator.apache.org/api/python/image/image.html#image-processing-functions
   - And there are very similar image augmenter functions like - ResizeAug, CenterCropAug, etc.. here - http://mxnet.incubator.apache.org/api/python/image/image.html#image-iterators
   
   Is there any specific reason for this kind of design? It might be good to take a relook at this and reorganize this, even if it leads to breaking a few APIs.
   
   And there is similar functionality in the gluon interface too( and I am not including that in this discussion).

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services