-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 04.02.2010 21:31, schrieb Fernando Perez: > Hi, > > I'm wondering why sphinx allows me to specify the path of the > directory to conf.py, but not the *actual file*, that seems to be > hardcoded to be named conf.py. It would be great to allow the > specification of the file by name, so that one could have > > conf-simple.py > conf-foo.py > conf-bar.py > > etc, and do different builds that share a lot of commonalities but > specify certain targets/options differently. Right now the only way I > can see of doing that is creating separate conf directories (with all > the path gymnastics that will require). > > Is there any reason why this hasn't been done? If no particular one, > would the devs be amenable to implementing it (I might even do it if > I need it badly enough, but I don't want to burn time if the issue is > undesired from the get go).
I think this hasn't been done because nobody needed it. I will accept a patch if you contribute it -- if you do, please simply extend handling of the -c option/confdir argument to either specify a directory *or* a file; in the latter case the confdir would be the dir of that file. cheers, Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAkuBSaQACgkQN9GcIYhpnLAxBQCggeKZcGZhMxy6QFEcbzQ4pFEZ INEAn1yRD12tFUG8ADYCyvibuuPP6Fb/ =8Ihc -----END PGP SIGNATURE----- -- 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.
