<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I’m +1 on this and I agree with Nathan’s comments. In particular, I think that we shouldn’t bundle them all into one package but probably split them off into separate packages. This requires more work on the behalf of the maintainers of those modules, of course.<div class=""><div class=""><br class=""></div><div class="">In addition to keeping in clump_finder, particle_trajectories should also probably be left in, and perhaps be turned into some kind of time series object or something else. </div><div class=""><br class=""></div><div class="">I’m happy to help out—in particular I can split off sunyaev_zeldovich and ppv_cube and spin them off as separate packages. photon_simulator is already deprecated in favor of pyXSIM.</div><div class=""><br class=""></div><div class="">All that spectral_integrator does is generate fields, so perhaps its functionality needs to be merged into the astro fields part somehow and left inside yt itself.</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Nov 22, 2016, at 8:54 PM, Nathan Goldbaum <<a href="mailto:nathan12343@gmail.com" class="">nathan12343@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">Overall I think this is a good idea. I have a couple critiques about the mechanics that I'll reply inline about. I think it makes sense to separate out all of the astro-specific analysis modules.<div class="gmail_extra"><br class=""><div class="gmail_quote">On Tue, Nov 22, 2016 at 8:37 PM, Britton Smith<span class="Apple-converted-space"> </span><span dir="ltr" class=""><<a href="mailto:brittonsmith@gmail.com" target="_blank" class="">brittonsmith@gmail.com</a>></span><span class="Apple-converted-space"> </span>wrote:<br class=""><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div dir="ltr" class=""><span id="gmail-m_2440452063024505651gmail-docs-internal-guid-14d1a6b0-8ed3-609f-b753-e59c9a72dec8" class=""><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">Greetings,</span></div><div dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><br class=""></div><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">I would like to open a discussion on the idea of moving most of yt’s analysis modules into an external yt extensions package. For ease of reading, I will separate this email into what this would mean for the code, what I see are the pros, cons, logistics, and open questions. I would very much appreciate comment on this.</span></div><div dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><br class=""></div><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; font-family: arial; background-color: transparent; font-weight: 700; vertical-align: baseline; white-space: pre-wrap;" class="">What this means</span></div><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">If we did this, most of the contents of </span><span style="font-size: 14.6667px; font-family: 'courier new'; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">yt/analysis_modules</span><span style="font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class=""> would be moved into a repository named something like </span><span style="font-size: 14.6667px; font-family: 'courier new'; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">yt_astro_analysis</span><span style="font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">. Installing this would be an option in the install script and would likely also be pip installable. Imports would change from</span></div><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; font-family: 'courier new'; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">from yt.analysis_modules.halo_<wbr class="">analysis.api import HaloCatalog</span></div><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">to</span></div><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; font-family: 'courier new'; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">from yt.extensions.astro_analysis.<wbr class="">halo_analysis.api import HaloCatalog</span></div><div dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><br class=""></div><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">After creating yt_astro_analysis, there would be a period where the old analysis_modules would still exist but be deprecated before being removed at some point down the road.</span></div><div dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><br class=""></div><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; font-family: arial; background-color: transparent; font-weight: 700; vertical-align: baseline; white-space: pre-wrap;" class="">Pros</span></div><ul style="margin-top: 0pt; margin-bottom: 0pt;" class=""><li dir="ltr" style="list-style-type: disc; font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline;" class=""><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">Almost all of the current analysis modules are specific to astrophysics. As we continue to make the core functionality of yt less astro specific, it’s not clear how to make room for non-astro analysis modules. Putting everything together under analysis_modules will make navigation and documentation messy and confusing. This would also significantly slim down the yt codebase.</span></div></li><li dir="ltr" style="list-style-type: disc; font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline;" class=""><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">Many of the tools in analysis_modules are very old and are in need of API-breaking refactor. Some of these, like two_point_functions, did not make the jump from yt-2 to yt-3 and are no longer usable. Many tools no longer have a champion, someone interested in using, maintaining, and updating them as yt’s core functionality develops and changes. Moving analysis_modules from yt decouples them from yt’s release cycle, allowing interested parties to make updates and releases on a separate, likely shorter timescale. Some analysis_modules may even be better suited to be moved into other extensions that are actively developed, such as the case of the AbsorptionSpectrum with the Trident project.</span></div></li><li dir="ltr" style="list-style-type: disc; font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline;" class=""><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">Similar to the point above, yt releases would not be slowed by the need to update all of the championless modules. Individual analysis modules can be tied to specific stable releases of yt and so assured to work there.</span></div></li></ul><div dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><br class=""></div><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; font-family: arial; background-color: transparent; font-weight: 700; vertical-align: baseline; white-space: pre-wrap;" class="">Cons</span></div><ul style="margin-top: 0pt; margin-bottom: 0pt;" class=""><li dir="ltr" style="list-style-type: disc; font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline;" class=""><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">This will take a non-zero amount of work. See below for a summary of the primary tasks.</span></div></li><li dir="ltr" style="list-style-type: disc; font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline;" class=""><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">There are some outstanding logistical questions. See below.</span></div></li><li dir="ltr" style="list-style-type: disc; font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline;" class=""><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">Not having yt and analysis modules explicitly tied to the same codebase/releases could result in analysis tools falling behind and out of date.</span></div></li><li dir="ltr" style="list-style-type: disc; font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline;" class=""><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">The disruption and need to alter scripts could irritate and alienate users.</span></div></li></ul><div dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><br class=""></div><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; font-family: arial; background-color: transparent; font-weight: 700; vertical-align: baseline; white-space: pre-wrap;" class="">Proposed progression</span></div><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">This is roughly how this would happen. Here is a table with all existing analysis modules, their status, and potential future: <a href="https://goo.gl/HZykQA" target="_blank" class="">https://goo.gl/HZykQA</a></span></div><ol style="margin-top: 0pt; margin-bottom: 0pt;" class=""><li dir="ltr" style="list-style-type: decimal; font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline;" class=""><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">Create yt_astro_analysis repo with all analysis modules that are to be moved. Add an entry to the extensions page on <a href="http://yt-project.org/" target="_blank" class="">yt-project.org</a>. Make it installed by default in the install script, at least at first.</span></div></li></ol></span></div></blockquote><div class=""><br class=""></div><div class="">Should there only be one repo? If we're going to do this, it might help future maintainability to have one repo per analysis module. That way maintainers that only care about one analysis module don't need to worry about changes to other modules.</div><div class=""><br class=""></div><div class="">I also don't think the clump finder in particular should be split out into its own package. That one isn't astro-specific and it might make sense to try to integrate it more deeply with the core of yt.</div><div class=""> </div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div dir="ltr" class=""><span id="gmail-m_2440452063024505651gmail-docs-internal-guid-14d1a6b0-8ed3-609f-b753-e59c9a72dec8" class=""><ol style="margin-top: 0pt; margin-bottom: 0pt;" class=""><li dir="ltr" style="list-style-type: decimal; font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline;" class=""><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">Deprecate all moved modules in yt.</span></div></li><li dir="ltr" style="list-style-type: decimal; font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline;" class=""><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">After some time, remove deprecated modules from yt.</span></div></li></ol><div dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><br class=""></div><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; font-family: arial; background-color: transparent; font-weight: 700; vertical-align: baseline; white-space: pre-wrap;" class="">Open issues</span></div><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">Here are some logistics and questions that still need to be worked out.</span></div><ul style="margin-top: 0pt; margin-bottom: 0pt;" class=""><li dir="ltr" style="list-style-type: disc; font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline;" class=""><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">Can we set up separate testing for yt_astro_analysis? Would maintaining this be a pain?</span></div></li></ul></span></div></blockquote><div class=""><br class=""></div><div class="">If the tests don't require large datasets and are relatively quick, this might be a good opportunity to explore bitbucket pipelines. There's also<span class="Apple-converted-space"> </span><a href="http://drone.io/" class="">drone.io</a><span class="Apple-converted-space"> </span>or we can use the yt testing infrastructure. Since I'm not the maintainer of the yt testing infra I can't speak to whether it's ok to expand it to more packages.</div><div class=""> </div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div dir="ltr" class=""><span id="gmail-m_2440452063024505651gmail-docs-internal-guid-14d1a6b0-8ed3-609f-b753-e59c9a72dec8" class=""><ul style="margin-top: 0pt; margin-bottom: 0pt;" class=""><li dir="ltr" style="list-style-type: disc; font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline;" class=""><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">How/where would the documentation be hosted?</span></div></li></ul></span></div></blockquote><div class=""><br class=""></div><div class="">Readthedocs will likely be sufficient. If we care about inline code examples or whatnot, then we can explore using the yt testing infrastructure, with the same caveats as above.</div><div class=""> </div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div dir="ltr" class=""><span id="gmail-m_2440452063024505651gmail-docs-internal-guid-14d1a6b0-8ed3-609f-b753-e59c9a72dec8" class=""><ul style="margin-top: 0pt; margin-bottom: 0pt;" class=""><li dir="ltr" style="list-style-type: disc; font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline;" class=""><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">How would we move the analysis modules source code and maintain its revision history?</span></div></li></ul></span></div></blockquote><div class=""><br class=""></div><div class="">This can be done relatively straightforwardly using the convert extension for mercurial and a filemap.<br class=""></div><div class=""> </div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div dir="ltr" class=""><span id="gmail-m_2440452063024505651gmail-docs-internal-guid-14d1a6b0-8ed3-609f-b753-e59c9a72dec8" class=""><div dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><br class=""></div><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; font-family: arial; background-color: transparent; font-weight: 700; vertical-align: baseline; white-space: pre-wrap;" class="">Questions to yt-dev</span></div><ul style="margin-top: 0pt; margin-bottom: 0pt;" class=""><li dir="ltr" style="list-style-type: disc; font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline;" class=""><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">Are you +/-1 on this? Any other comments?</span></div></li></ul></span></div></blockquote><div class=""><br class=""></div><div class="">+1</div><div class=""> </div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div dir="ltr" class=""><span id="gmail-m_2440452063024505651gmail-docs-internal-guid-14d1a6b0-8ed3-609f-b753-e59c9a72dec8" class=""><ul style="margin-top: 0pt; margin-bottom: 0pt;" class=""><li dir="ltr" style="list-style-type: disc; font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline;" class=""><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">Changes to the analysis_modules spreadsheet (</span><a href="https://goo.gl/HZykQA" target="_blank" style="text-decoration: none;" class=""><span style="font-size: 14.6667px; background-color: transparent; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;" class="">https://goo.gl/HZykQA</span></a><span style="font-size: 14.6667px; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">)?</span></div></li><li dir="ltr" style="list-style-type: disc; font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline;" class=""><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">Interested in helping out with this? If this happens, I propose anyone interested meets for a hangout to discuss how to proceed.</span></div></li></ul></span></div></blockquote><div class=""><br class=""></div><div class="">I'm happy to help.</div><div class=""> </div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div dir="ltr" class=""><span id="gmail-m_2440452063024505651gmail-docs-internal-guid-14d1a6b0-8ed3-609f-b753-e59c9a72dec8" class=""><div dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><br class=""></div><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">Thanks for reading!</span></div><span class="gmail-HOEnZb"><font color="#888888" class=""><div dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=""><br class=""></div><span style="font-size: 14.6667px; font-family: arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">Britton</span></font></span></span><br class=""></div><br class="">______________________________<wbr class="">_________________<br class="">yt-dev mailing list<br class=""><a href="mailto:yt-dev@lists.spacepope.org" class="">yt-dev@lists.spacepope.org</a><br class=""><a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" rel="noreferrer" target="_blank" class="">http://lists.spacepope.org/<wbr class="">listinfo.cgi/yt-dev-spacepope.<wbr class="">org</a><br class=""><br class=""></blockquote></div><br class=""></div></div><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">_______________________________________________</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">yt-dev mailing list</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><a href="mailto:yt-dev@lists.spacepope.org" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">yt-dev@lists.spacepope.org</a><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a></div></blockquote></div><br class=""></div></div></body></html>