Description
I would like to use enum_tools for a conda package which I plan to publish at conda-forge. One of my dependencies is your module. As you already made enum_tools available at your own conda channel, would you mind adding conda-forge as an additional channel?
The general issue is that with our own personal channels, we will end up with a long chain of additional channels. Now it is conda-build -c conda-forge -c domdfcoding my-recipe for me when building my package on my own channel. But the next person who depends on my work would need to add my personal channel as well, making this chain longer and longer. This is not good practice. Some interesting background knowledge is available at https://github.com/conda-forge/staged-recipes#6-do-all-of-my-packages-dependencies-have-to-be-in-conda-forge-already.
Quick side note: This is only necessary because I need enum_tools for the user installation (otherwise the decorators would not be defined). If it was only a dependency for the development installation (as layed out in #50), this step could be skipped.
Alternative: A possible workaround would be to define my own wrapper for your library, checking whether it is installed and if it is not available, just make the decorators a no-op. This is by far not my favorite solution.