5 ms·
I consider it a nice-to-have, but we can definitely remove it if deemed unnecessary. Want to open an issue about it?
by kenneth_reitz 9y ago
I consider it a nice-to-have, but we can definitely remove it if deemed unnecessary. Want to open an issue about it?
- friendlydude12 9y agoThat’s just my preference. Keep the features that are best for your specific use cases. It’s your project after all. I think that’s better than design by committee. Linus didn’t write Linux for other people.
- nojvek 9y agoIf you’re doing markdown conversion well, keep it. Apis are not about doing the smallest thing, it’s about designing a clean abstraction of a problem you’re trying to solve.
- friendlydude12 9y agoSure, if APIs existed within a vacuum. In the real world we have to worry about ease of packaging, ease of maintenance, and various other practical costs.
- 3pt14159 9y agoFor what it is worth, I strongly prefer leaving it in. Sometimes I want to just generate documentation for different things based on different sources and being able to just clean the html by rendering to Markdown would be great.
- mixmastamyk 9y agoCould be made an optional feature in setup.py.
- arikfr 9y agoI personally find it useful, although I can see why it feels out of place. If you do decide to remove it, I think it's worth adding as an example in the README.
- EmilStenstrom 9y agoDefinitely shouldn’t be there.