Hello,

It seems like every third build or so, sphinx decides that the config
file has changed and forces a full rebuild of all content. While I
appreciate its caution in this regard, it is a bit this is frustrating.

I suspect that what's happening is that a changed environment variable
confuses Sphinx into thinking that the config has changed and/o*or* that when
the file is touched (as in the case when changing the git branch,) it
thinks that the config has changed, when in fact it has not. 

My request, then, is for a better understanding of how the config
hashing/caching works: 

1. Is one of my theories correct?

2. If not, where in the code should I look to find an answer?

3. Does anyone else experience this, and what have you done to address
   this issue?
   
Cheers,
sam

-- 
Sam Kleinman (tychoish): 
 - ga...@tychoish.com
 - tychoish <http://tychoish.com/>
 "don't get it right, get it written" -- james thurber

Attachment: pgpCE1UhOclGi.pgp
Description: PGP signature

Reply via email to