-
-
Notifications
You must be signed in to change notification settings - Fork 106
Expand file tree
/
Copy pathindex.html
More file actions
529 lines (434 loc) · 23.8 KB
/
index.html
File metadata and controls
529 lines (434 loc) · 23.8 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
<!DOCTYPE html>
<html xmlns="https://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="description" content="Astropy. A Community Python Library for Astronomy." />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<link rel="shortcut icon" href="../favicon.ico" />
<link href="https://fonts.googleapis.com/css?family=Open+Sans:400italic,400,700" rel="stylesheet" type="text/css" />
<link rel="stylesheet" type="text/css" href="../css/style.css" />
<link rel="stylesheet" type="text/css" href="../css/jquery.sidr.light.css" />
<title>Astropy | Affiliated Packages</title>
<!-- Google analytics -->
<script src="../js/analytics.js"></script>
</head>
<body>
<div id="wrapper">
<nav>
<div id="mobile-header">
<!-- Menu Icon -->
<a id="responsive-menu-button" href="#sidr-main"><div><svg senable-background="new 0 0 24 24" height="24px" id="Layer_1" version="1.1" viewBox="0 0 24 24" width="24px" x="0px" xml:space="preserve" xmlns="https://www.w3.org/2000/svg" xmlns:xlink="https://www.w3.org/1999/xlink" y="0px"><g><g><path d="M23.244,17.009H0.75c-0.413,0-0.75,0.36-0.75,0.801v3.421C0,21.654,0.337,22,0.75,22h22.494c0.414,0,0.75-0.346,0.75-0.77 V17.81C23.994,17.369,23.658,17.009,23.244,17.009z M23.244,9.009H0.75C0.337,9.009,0,9.369,0,9.81v3.421 c0,0.424,0.337,0.769,0.75,0.769h22.494c0.414,0,0.75-0.345,0.75-0.769V9.81C23.994,9.369,23.658,9.009,23.244,9.009z M23.244,1.009H0.75C0.337,1.009,0,1.369,0,1.81V5.23c0,0.423,0.337,0.769,0.75,0.769h22.494c0.414,0,0.75-0.346,0.75-0.769V1.81 C23.994,1.369,23.658,1.009,23.244,1.009z"/></g></g></svg></div></a>
<!-- -->
</div>
<a href="../index.html"><img src="../images/astropy_word.svg" height="32" onerror="this.src='../images/astropy_word_32.png; this.onerror=null;"/></a>
<div id="navigation">
<ul>
<li>
<div class="dropdown">
<a>About</a>
<div class="dropdown-content">
<ul>
<li><a href="../about.html">About Astropy</a></li>
<li><a href="../code_of_conduct.html">Code of Conduct</a></li>
<li><a href="../acknowledging.html">Acknowledging & Citing</a></li>
<li><a href="history.html">History</a></li>
</ul>
</div>
</div>
</li>
<li><a href="../help.html">Get Help</a></li>
<li><a href="../contribute.html">Contribute</a></li>
<li>
<div class="dropdown">
<a href="https://docs.astropy.org">Documentation</a>
<div class="dropdown-content">
<ul>
<li><a href="https://docs.astropy.org" target="_blank">Current Release</a></li>
<li><a href="https://astropy.readthedocs.io/en/latest/" target="_blank">In Development</a></li>
</ul>
</div>
</div>
</li>
<li><a href="index.html">Affiliated Packages</a></li>
<li><a href="../team.html">Team</a></li>
</ul> </div>
<div class="search pull-right">
<form action="https://docs.astropy.org/en/stable/search.html" method="get">
<input type="text" name="q" placeholder="Search Documentation" />
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
</div>
</nav>
<section>
<h1 id="affiliated-packages">Astropy Affiliated Packages<a class="paralink" href="#affiliated-packages" title="Permalink to this headline">¶</a></h1>
<p>A major part of the Astropy Project is the concept of “Astropy
affiliated packages”. An affiliated package is an astronomy-related Python
package that is not part of the astropy core package, and is not managed by
the project but is a part of the Astropy Project community. These packages
demonstrate a commitment to Astropy’s goals of improving reuse,
interoperability, and interface standards for Python astronomy and
astrophysics packages. In many (but not all) cases, affiliated packages
also follow similar development processes and package templates as for the
core package.</p>
<p>If you are a developer interested in signing up as an affiliated package,
details are in the <a href="#affiliated-instructions">Becoming an
Affiliated Package</a> section.</p>
<h1 id="coordinated-packages">Astropy Coordinated Packages<a class="paralink" href="#coordinated-packages" title="Permalink to this headline">¶</a></h1>
<p>A related concept is that of “Astropy coordinated packages”. Coordinated
packages are similar to affiliated packages, but the Astropy Project as a
whole maintains them. In practice this means the Astropy coordination
committee has administrative control of a coordinated package repository
(delegated to the maintainers), and that maintainers of these packages have
<a href="../team.html"> formal roles</a> in the Astropy Project. The most
prominent of these coordinated packages is the Astropy core package itself.
In some cases these are packages identified by the core team as needing
development separate from the core (either they are experimental or problem
space-focused), while others started as affiliated packages but have become
so important to the ecosystem that they grew to become coordinated.</p>
<h1 id="infrastructure-packages">Astropy Infrastructure Packages<a class="paralink" href="#infrastructure-packages" title="Permalink to this headline">¶</a></h1>
<p>One final related category are the "Astropy infrastructure packages".
These packages are those that are necessary infrastructure for Astropy
packages - e.g. testing and documentation machinery. While occasionally
these have astro-specific functionality, in general they are more generic
packages that are useful to packages outside of astronomy, and as a result
may have some maintainers outside the Astropy project. But some are also
Astropy coordinated packages, with maintainers drawn from the infrastructure
roles.
</p>
</section>
<section id="installing">
<h1 id="installing-affiliated-packages">Installing Affiliated and Coordinated Packages<a class="paralink" href="#installing-affiliated-packages" title="Permalink to this headline">¶</a></h1>
<p>All packages should be available on PyPI. Some are available via conda, particularly
through the conda-forge channel. That said, affiliated packages are developed
independently of the Astropy core library. You should refer to the package's
documentation first if you encounter problems.</p>
</section>
<!-- NOTE: We still use affiliated/registry.json for this. -->
<section id="coordinated-package-registry">
<h1 id="coordinated-package-list">Coordinated Packages<a class="paralink" href="#coordinated-package-list" title="Permalink to this headline">¶</a></h1>
<p>The following table lists all current Astropy coordinated packages.</p>
<p>Total number of coordinated packages: <strong id="total-coordinated-pkgs"></strong></p>
<table border="1" class="docutils" id="coordinated-package-table">
<colgroup>
<col width="5%" />
<col width="3%" />
<col width="3%" />
<col width="10%" />
</colgroup>
<thead valign="bottom">
<tr class="row-odd">
<th class="head"></th>
<th class="head"></th>
<th class="head"></th>
<th class="head"></th>
</tr>
</thead>
<tbody valign="top">
<tr class="row-even"><td rowspan="1">Loading...</td>
<td rowspan="1"> </td>
<td rowspan="1"> </td>
<td rowspan="1"> </td>
<td rowspan="1"> </td>
</tr>
<tr class="row-odd">
<td colspan="1"> </td>
<td colspan="3"> </td>
</tr>
</tbody>
</table>
</section>
<section id="affiliated-package-registry">
<h1 id="affiliated-package-list">Affiliated Packages Registry<a class="paralink" href="#affiliated-package-list" title="Permalink to this headline">¶</a></h1>
<p>The following table lists all currently registered affiliated packages.</p>
<p>NOTE: The listing is currently minimal because Astropy has just accepted
<a href="https://github.com/astropy/astropy-APEs/blob/main/APE22.rst">APE 22</a>
in January 2024. We are in the midst of transitioning to the new process in
partnership with pyOpenSci, so we really appreciate your patience.
</p>
<p>Total number of post-APE 22 affiliated packages: <strong id="total-pyos-pkgs"></strong></p>
<table border="1" class="docutils" id="pyos-package-table">
<colgroup>
<col width="5%" />
<col width="3%" />
<col width="3%" />
<col/>
</colgroup>
<thead valign="bottom">
<tr class="row-odd">
<th class="head"></th>
<th class="head"></th>
<th class="head"></th>
<th class="head"></th>
</tr>
</thead>
<tbody valign="top">
<tr class="row-even">
<td colspan="1"> </td>
<td colspan="3"> </td>
</tr>
<tr class="row-odd">
<td colspan="1"> </td>
<td colspan="3"> </td>
</tr>
</tbody>
</table>
<!-- TODO: We have promised pyOpenSci that we would also link back to their canonical listing
here, with their Astropy filter applied. Waiting for resolution of
https://github.com/pyOpenSci/software-peer-review/issues/268
but for now just do a generic link to their listing. -->
<p>All accepted pyOpenSci packages available <a href="https://www.pyopensci.org/communities/astropy.html">here</a>.</p>
<p>All currently under review packages via pyOpenSci available <a href="https://github.com/pyOpenSci/software-submission/issues?q=is%3Aissue+is%3Aopen+label%3Aastropy">here</a>.</p>
</section>
<section id="affiliated-package-registry-pre-ape22">
<h1 id="affiliated-package-list-pre-ape22">Affiliated Packages Registry (Pre-APE 22)<a class="paralink" href="#affiliated-package-list-pre-ape22" title="Permalink to this headline">¶</a></h1>
<p>This section contains the listing of Astropy Affiliated Packages that pre-dated
<a href="https://github.com/astropy/astropy-APEs/blob/main/APE22.rst">APE 22</a>.
No new packages are added to this list after March 6, 2024; but packages can be removed or their
status can change. In particular packages that are archived by their maintainers or are no longer actively maintained, can be moved to the
<a href="#affiliated-package-list-emeritus">emeritus section</a>.
</p>
<p>A detailed description of the meaning of the badges for each package can be found
<a
href="https://github.com/astropy/astropy-project/blob/a9ea09ccd27703ea3ef2a80a811a5f70f91bc94b/affiliated/affiliated_package_review_guidelines.md#development-status-devstatus">here</a>.
</p>
<p>Total number of pre-APE 22 affiliated packages: <strong id="total-affiliated-pkgs"></strong></p>
<table border="1" class="docutils" id="affiliated-package-table">
<colgroup>
<col width="5%" />
<col width="3%" />
<col width="3%" />
<col/>
</colgroup>
<thead valign="bottom">
<tr class="row-odd">
<th class="head"></th>
<th class="head"></th>
<th class="head"></th>
<th class="head"></th>
</tr>
</thead>
<tbody valign="top">
<tr class="row-even"><td rowspan="1">Loading...</td>
<td rowspan="1"> </td>
<td rowspan="1"> </td>
<td rowspan="1"> </td>
<td rowspan="1"> </td>
</tr>
<tr class="row-odd">
<td colspan="1"> </td>
<td colspan="3"> </td>
</tr>
</tbody>
</table>
<section id="affiliated-package-registry-emeritus">
<h1 id="affiliated-package-list-emeritus">Archived/Emeritus Affiliated Packages<a class="paralink"
href="#affiliated-package-list-emeritus" title="Permalink to this headline">¶</a></h1>
<p>This section contains a list of packages that are no longer actively maintained, that means that they might
no longer work with the most recent release of Python or Astropy and do not receive new features or bug fixes.
However, some of those packages still provide unique
capabilities that no newer package matches or are still widely used.
</p>
<p>If there is new active development, the package can be moved back into <a href="#affiliated-package-list-pre-ape22">the pre-APE 22 list</a>;
if you are interested in taking over development from one of these packages we recommend contacting the maintainer or reach out to the Astropy
community.
</p>
<p>Total number of archived/emeritus affiliated packages: <strong id="total-emeritus-pkgs"></strong></p>
<table border="1" class="docutils" id="emeritus-package-table">
<colgroup>
<col width="5%" />
<col width="3%" />
<col width="3%" />
<col />
</colgroup>
<thead valign="bottom">
<tr class="row-odd">
<th class="head"></th>
<th class="head"></th>
<th class="head"></th>
<th class="head"></th>
</tr>
</thead>
<tbody valign="top">
<tr class="row-even">
<td rowspan="1">Loading...</td>
<td rowspan="1"> </td>
<td rowspan="1"> </td>
<td rowspan="1"> </td>
<td rowspan="1"> </td>
</tr>
<tr class="row-odd">
<td colspan="1"> </td>
<td colspan="3"> </td>
</tr>
</tbody>
</table>
</section>
<section id="affiliated-instructions">
<h1 id="becoming-an-affiliated-package">Becoming an Affiliated Package<a class="paralink" href="#becoming-an-affiliated-package" title="Permalink to this headline">¶</a></h1>
<p>Astropy <a href="https://www.pyopensci.org/partners.html">uses the pyOpenSci peer review process</a>
to vet affiliated packages. If you are a developer of an astronomy package and would like your package to become
affiliated with the Astropy Project, you submit your package directly to pyOpenSci.
Astropy will be involved in the review, which will allow your package to become an
affiliated package through that review process. You can also opt to be fast tracked through
<a href="https://joss.theoj.org/">JOSS</a> if desired. Read the pyOpenSci author guide to learn
<a href="https://www.pyopensci.org/software-peer-review/how-to/author-guide.html">
how to get started with submitting a package to pyOpenSci through their affiliated partner program Guidebook</a>.
</p>
<p>In addition to pyOpenSci criteria, we also apply
<a href="https://github.com/astropy/astropy-project/blob/main/affiliated/affiliated_package_review_guidelines.md">
Astropy-specific guidelines for reviewing affiliated packages</a>.
This will give you a
sense of whether your package is ready for review. Broadly speaking, your
package should:</p>
<ul>
<li>Comply with general pyOpenSci review standards. Please see <a href="https://www.pyopensci.org/software-peer-review/how-to/author-guide.html">Peer Review Guide for Python Open Source Authors</a> for more details.</li>
<li>Be potentially useful to astronomers. This can mean useful to a
specific sub-domain of astronomy, or more broadly useful to a large
fraction of astronomy (or beyond, as long as it is also useful for
astronomy).</li>
<li>Specifically use, interface with, or provide complementary capabilities
to other Astropy packages.</li>
<li>Use <a href="https://docs.astropy.org/">classes and functions from the
astropy core package</a> wherever possible and appropriate, and (as much as
possible) avoid duplication with other packages in the Astropy ecosystem.
This facilitates re-use of code and sharing of resources.</li>
<li>Be open to contributions from others. While this most straightforwardly
means it follows a Github-based open development model (like the Astropy core
package), alternative approaches are perfectly valid as long as they are
consistent with basic principles of open source; e.g.,
<a href="https://choosealicense.com/">an OSI-approved license</a>.</li>
<li>Include instructions to users on how to cite your package. This is commonly done
with a CITATION file. This file could include a Zenodo record (highly recommended),
acknowledgement text, and/or journal article(s). Where possible, full BibTeX entries of
these citations are recommended.</li>
<li>Include citations to other relevant papers and software following
<a href="https://www.astrobetter.com/blog/2019/07/01/citing-astronomy-software-inline-text-examples/">leading
practices for citing astronomy software</a>.</li>
</ul>
</p>
<p>In addition, you should make an effort to connect with the Astropy
developer community, including developers from the core astropy package or
any related affiliated packages. If your package is determined to meet the above
standards, it will be accepted and added to the affiliated package registry.
Note however that if packages become unmaintained or do not meet the standards
anymore, they may be removed from the list of affiliated packages, <a href="https://www.pyopensci.org/software-peer-review/our-process/policies.html#after-acceptance-package-ownership-and-maintenance">as per pyOpenSci policy.</a></p>
<h2 id="package-template">Package Template<a class="paralink" href="#package-template" title="Permalink to this headline">¶</a></h2>
<p>If you are considering creating a new astronomy package and would like it
to be an Astropy affiliated package, you can use <a href="https://github.com/OpenAstronomy/packaging-guide">the OpenAstronomy packaging guide</a> to
make it much easier to meet these standards. It reflects up-to-date Python packaging techniques
to generate documentation like that used in the astropy package, a
ready-to-use testing framework, and a variety of tools that streamline tasks
like user configuration, caching downloaded files, or linking C-compiled
extensions. More details on this template are available in the <a
href="https://packaging-guide.openastronomy.org/en/latest/#using-the-template">usage
instructions for the template</a>.
</p>
<p>Additionally, it is also acceptable to use
<a href="https://www.pyopensci.org/python-package-guide/index.html">pyOpenSci Python Package Guide</a>
if you think that better suits your package needs.</p>
<p>We recommend that you join the <a href="https://groups.google.com/forum/#!forum/astropy-affiliated-maintainers">astropy-affiliated-maintainers</a> mailing list to be kept informed of any dicussions related to affiliated packages.</p>
</section>
<section id="affiliated-faqs">
<h1 id="affiliated-package-faqs">Affiliated Package: FAQs<a class="paralink" href="#affiliated-package-faqs" title="Permalink to this headline">¶</a></h1>
<h2 id="affil-new-pkg">I want my package to be Astropy Affiliated<a class="paralink" href="#affil-new-pkg" title="Permalink to this headline">¶</a></h2>
<p>Thank you for your interest! Please see <a href="#becoming-an-affiliated-package">Becoming an Affiliated Package</a> above. When in doubt, feel free to contact Astropy Affiliated Editors for advice.</p>
<h2 id="affil-maintainer-no-time">I no longer have time to maintain my Astropy Affiliated package<a class="paralink" href="#affil-maintainer-no-time" title="Permalink to this headline">¶</a></h2>
<p>Please contact pyOpenSci, as per <a href="https://www.pyopensci.org/software-peer-review/our-process/policies.html#peer-review-guidelines-policies">Peer Review Guidelines & Policies</a>.</p>
<h2 id="affil-pkg-delist">I want to delist my package as Astropy Affiliated<a class="paralink" href="#affil-pkg-delist" title="Permalink to this headline">¶</a></h2>
<p>Please see <a href="https://www.pyopensci.org/software-peer-review/our-process/policies.html#requesting-package-removal-from-the-pyopensci-ecosystem">Requesting package removal from the pyOpenSci ecosystem</a>.</p>
<h2 id="new-affil-editor">I am a new Editor<a class="paralink" href="#new-affil-editor" title="Permalink to this headline">¶</a></h2>
<p>Welcome and thank you! We usually do not switch out all our Editors at the same time,
so the incumbent co-Editor could help you contact pyOpenSci to add you to
<a href="https://www.pyopensci.org/about-peer-review/#meet-our-editorial-board">pyOpenSci editorial board</a>
with the understanding that we are taking the person you are replacing off that board
and that your role is Astropy- and astronomy-focused.</p>
<p>Your name would also be added to <a href="../team.html">Astropy Team</a> under the same role.</p>
<h2 id="new-affil-reviewer">I am a new reviewer<a class="paralink" href="#new-affil-reviewer" title="Permalink to this headline">¶</a></h2>
<p>Welcome and thank you! Please submit the sign-up form that can be found under
<a href="https://www.pyopensci.org/about-peer-review/#get-involved-with-peer-review">Become a pyOpenSci reviewer</a>. Do not forget to check "Astropy"/"astronomy"/"astrophysics"
when you see them as options.</p>
<p>It is important that you understand your reviews will be done in public. There is no option to remain anonymous.</p>
</section>
<footer>
<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js"></script>
<script src="../js/jquery.sidr.min.js"></script>
<script src="../js/functions.js"></script>
<script type="text/javascript">
$(document).ready(function() {
$.getJSON("registry.json", populateTables);
});
</script>
<!-- Tom Donaldson: The idea was to use the existing YAML parser that works fine in nodejs,
but bundle it for use in a client. So I created yaml_parse.js
import parse from 'yaml'
window.yaml = parse;
and then bundled it with a bundler I found called esbuild:
npm install --save-exact --save-dev esbuild
./node_modules/.bin/esbuild yaml_parse.js --bundle --minify --outfile=yaml_parse_bundle.js
-->
<script src="../js/yaml_parse_bundle.js"></script>
<script>
fetch('https://raw.githubusercontent.com/pyOpenSci/pyopensci.github.io/main/_data/packages.yml')
.then(response => response.text())
.then(yamlString => {
var parsed = yaml.parse(yamlString);
var i = 0;
var tab = document.getElementById("pyos-package-table");
// Sort alphabetically by package name (case-insensitive)
parsed.sort((a, b) => a.package_name.toLowerCase().localeCompare(b.package_name.toLowerCase()));
var info = "";
for (var p=0; p<parsed.length; p++) {
var package = parsed[p];
var partners = package["labels"];
if (partners == null) {
continue;
}
let found_astropy = partners.some(e => e.includes("astropy"));
if (!found_astropy) {
continue;
}
namerow = tab.insertRow(-1);
nmcell = namerow.insertCell(0);
urlcell = namerow.insertCell(1);
repocell = namerow.insertCell(2);
pypicell = namerow.insertCell(3);
nmcell.innerHTML = package["package_name"];
nmcell.className = 'first-package-row'
nmcell.setAttribute('width', 100)
urlcell.innerHTML = url_translator(package["gh_meta"]["documentation"]);
repocell.innerHTML = repo_translator(package["repository_link"]);
//pypicell.innerHTML = pypi_translator(package["package_name"]); // FIXME: https://github.com/pyOpenSci/pyopensci.github.io/issues/390
descrow = tab.insertRow(-1);
descrow.insertCell(0).innerHTML = "";
desccell = descrow.insertCell(1);
desccell.colSpan = "3";
desccell.innerHTML = package["package_description"];
var maintainers = package["all_current_maintainers"];
var maintainers_str = "";
for (var m=0; m<maintainers.length; m++) {
maintainers_str += ghuser_translator(maintainers[m]["name"], maintainers[m]["github_username"]);
if (m < (maintainers.length - 1)) {
maintainers_str += ", ";
}
}
maintrow = tab.insertRow(-1);
maintrow.insertCell(0).innerHTML = "";
maintcell = maintrow.insertCell(1);
maintcell.colSpan = "3";
maintcell.innerHTML = "Maintainer(s): " + maintainers_str;
i += 1;
}
document.getElementById("total-pyos-pkgs").innerHTML = i;
;
});
</script>
<hr>
<p>
<img style="vertical-align:middle" src="../images/astropy_brandmark.png" height=20><span style="vertical-align:middle">
<a href="../code_of_conduct.html"> The Astropy Project is committed to fostering an inclusive community</a></span>.
</p>
</footer>
</div>
</body>
</html>