Among the utilities scrapy has to make it's own development easier
I bumped on scrapy.utils.misc.load_object. I'd like to use this utility
while being sure that it won't change without at least going through
deprecation and removal on a next release.

I write extensions and one needs a class that should live inside
the scrapy project. In the settings file, references to classes
are often written as strings which use the dot notation for python
imports. These are mostly read by internal parts that wouldn't need
documentation but some builtin extensions/middlewares also use it.
So reused it.
These builtins, I suspect, served as examples more people than me
so it wouldn't surprise me if others went the same way.

I suggest documenting it to ensure it will not be abruptly removed.
I want to open a PR/ticket for this but do you (developers) agree
on the suggestion or would I just waste time on it?

-- 
You received this message because you are subscribed to the Google Groups 
"scrapy-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/scrapy-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to