Chris Withers wrote: > Thomas G. Willis wrote: >> I guess what I would like to have is something like... >> >> c:\project\myegg-src>python setup.py bdist_egg >> >> to produce... >> >> ./myegg-0.0 >> ..../docs >> ..../myegg >> ..../tests >> >> But I'm not quite grokking how to get this to work. > > Why would you want to include docs in an egg? An egg is not designed to > have content read by humans ;-) > > Docs in a sdist, yes, that makes sense and I have the same questions you > do, but bdist_* makes no sense...
Because.... ? If I want to download a package, I likewise want to know how to use it. I certainly don't want to have to download a separate package just for the docs -- unless they're absolutely huge or have some kind of ecosystem of their own which makes them an application in their own right. TJG --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en -~----------~----~----~----~------~----~------~--~---
