@@ -182,24 +182,32 @@ and change the cache location. Caching persists between Astroquery sessions.
182
182
If you know the service you are using has released new data recently, or if you believe you are
183
183
not recieving the newest data, try clearing the cache.
184
184
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:
187
193
188
194
.. code-block :: python
189
195
196
+ >> > from astroquery import conf
190
197
>> > from astroquery.simbad import Simbad
191
198
192
199
>> > # Is the cache active?
193
- >> > print (Simbad .cache_active)
200
+ >> > print (conf .cache_active)
194
201
True
195
202
203
+ >> > # Cache timout in seconds
204
+ >> > print (conf.cache_timeout)
205
+ 604800
206
+
196
207
>> > # Cache location
197
208
>> > print (Simbad.cache_location)
198
209
/ Users/ username/ .astropy/ cache/ astroquery/ Simbad
199
210
200
- >> > # Cache timout in seconds
201
- >> > print (Simbad.cache_timeout)
202
- 604800
203
211
204
212
205
213
Available Services
0 commit comments