@@ -182,24 +182,32 @@ and change the cache location. Caching persists between Astroquery sessions.
182182If you know the service you are using has released new data recently, or if you believe you are
183183not recieving the newest data, try clearing the cache.
184184
185- The Astroquery cache is divided by service, so each service's cache should be managed invidually.
186- Shown here are the cache properties, using Simbad as an example.
185+
186+ The Astroquery cache location is divided by service, so each service's cache should be managed invidually,
187+ however whether the cache is active and the expiration time are controlled centrally through the
188+ astroquery ``conf `` module. Astroquery uses the Astropy configuration infrastructure, information about
189+ temporarily or permanently changing configuration values can be found
190+ `here <https://docs.astropy.org/en/latest/config/index.html >`_.
191+
192+ Shown here are the cache properties, using Simbad as an example:
187193
188194.. code-block :: python
189195
196+ >> > from astroquery import conf
190197 >> > from astroquery.simbad import Simbad
191198
192199 >> > # Is the cache active?
193- >> > print (Simbad .cache_active)
200+ >> > print (conf .cache_active)
194201 True
195202
203+ >> > # Cache timout in seconds
204+ >> > print (conf.cache_timeout)
205+ 604800
206+
196207 >> > # Cache location
197208 >> > print (Simbad.cache_location)
198209 / Users/ username/ .astropy/ cache/ astroquery/ Simbad
199210
200- >> > # Cache timout in seconds
201- >> > print (Simbad.cache_timeout)
202- 604800
203211
204212
205213 Available Services
0 commit comments