<div dir="ltr"><div>Not 100% sure. It certainly won't work on OS X at the moment.<br></div><div><br></div><div>-Nathan</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Sep 10, 2013 at 10:59 AM, Matthew Turk <span dir="ltr"><<a href="mailto:matthewturk@gmail.com" target="_blank">matthewturk@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Nathan,<br>
<div class="im"><br>
On Tue, Sep 10, 2013 at 1:16 PM, Nathan Goldbaum <<a href="mailto:nathan12343@gmail.com">nathan12343@gmail.com</a>> wrote:<br>
> Hey John,<br>
><br>
> A few questions:<br>
><br>
> 1. What did you choose for INST_YT_SOURCE in get_yt.sh? If INST_YT_SOURCE=1,<br>
> what happens when you try INST_YT_SOURCE=0?<br>
><br>
> 2. Again, if you had INST_YT_SOURCE=1, when you manually run `setup.py<br>
> install` in the yt source repository, it should print out a few lines<br>
> showing the root directory for the PNG, Freetype, and HDF5 libraries it<br>
> tries to link against. This should be the very first thing printed out by<br>
> the setup script. Is it linking against anaconda's libraries or system<br>
> libraries?<br>
><br>
> 3. What's the output of `ldd<br>
> /u/jzuhone/anaconda/lib/python2.7/site-packages/yt/utilities/lib/png_writer.so`?<br>
><br>
> I'm beginning to suspect that we cannot link against the libraries provided<br>
> by anaconda unless we tailor our build environment to match the sort of<br>
> gymnastics that `conda build` does to sanitize the build environment. Just<br>
> yesterday I was having no end of grief trying to link against anaconda's<br>
> hdf5 library. yt is able to link against this library inside a conda build<br>
> environment, but when I try to link in my normal shell environment I run<br>
> into issues - mostly because the OS X hdf5 library on anaconda was compiled<br>
> on an OS X 10.5 machine.<br>
<br>
</div>If I read you correctly, you are saying that, practically speaking,<br>
this would mainly mean not using the yt-conda HDF5 for Enzo/FLASH/etc<br>
outside of yt. Right?<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
><br>
> On Tue, Sep 10, 2013 at 9:54 AM, John ZuHone <<a href="mailto:jzuhone@gmail.com">jzuhone@gmail.com</a>> wrote:<br>
>><br>
>> Hi Nathan and all,<br>
>><br>
>> Here's a little more info on that error you asked about regarding glibc.<br>
>> It came up again for me on Pleiades, this time with yt itself.<br>
>><br>
>> Traceback (most recent call last):<br>
>> File "/u/jzuhone/anaconda/bin/yt", line 4, in <module><br>
>> from yt.utilities.command_line import run_main<br>
>> File<br>
>> "/u/jzuhone/anaconda/lib/python2.7/site-packages/yt/utilities/command_line.py",<br>
>> line 29, in <module><br>
>> from yt.mods import *<br>
>> File "/u/jzuhone/anaconda/lib/python2.7/site-packages/yt/mods.py", line<br>
>> 60, in <module><br>
>> from yt.data_objects.api import \<br>
>> File<br>
>> "/u/jzuhone/anaconda/lib/python2.7/site-packages/yt/data_objects/api.py",<br>
>> line 31, in <module><br>
>> from grid_patch import \<br>
>> File<br>
>> "/u/jzuhone/anaconda/lib/python2.7/site-packages/yt/data_objects/grid_patch.py",<br>
>> line 35, in <module><br>
>> from yt.data_objects.data_containers import YTFieldData<br>
>> File<br>
>> "/u/jzuhone/anaconda/lib/python2.7/site-packages/yt/data_objects/data_containers.py",<br>
>> line 45, in <module><br>
>> from yt.data_objects.derived_quantities import GridChildMaskWrapper<br>
>> File<br>
>> "/u/jzuhone/anaconda/lib/python2.7/site-packages/yt/data_objects/derived_quantities.py",<br>
>> line 36, in <module><br>
>> from yt.utilities.parallel_tools.parallel_analysis_interface import \<br>
>> File<br>
>> "/u/jzuhone/anaconda/lib/python2.7/site-packages/yt/utilities/parallel_tools/parallel_analysis_interface.py",<br>
>> line 39, in <module><br>
>> from yt.utilities.lib import \<br>
>> File<br>
>> "/u/jzuhone/anaconda/lib/python2.7/site-packages/yt/utilities/lib/__init__.py",<br>
>> line 35, in <module><br>
>> from .png_writer import *<br>
>> ImportError: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by<br>
>> /u/jzuhone/anaconda/lib/python2.7/site-packages/yt/utilities/lib/png_writer.so)<br>
>><br>
>> Best,<br>
>><br>
>> John<br>
>><br>
>> On Sep 3, 2013, at 3:10 PM, Nathan Goldbaum <<a href="mailto:nathan12343@gmail.com">nathan12343@gmail.com</a>> wrote:<br>
>><br>
>> John, can you give a little more info on that error? I'm a little<br>
>> concerned that there are binary incompatibilities that conda can't resolve.<br>
>> Perhaps this is something we should report on the conda issue tracker.<br>
>><br>
>> Matt, can't we get the recipes in the same way we get the latest dev<br>
>> install script? Something like:<br>
>><br>
>> wget <a href="https://bitbucket.org/yt_analysis/yt_conda/raw/yt/meta.yaml" target="_blank">https://bitbucket.org/yt_analysis/yt_conda/raw/yt/meta.yaml</a><br>
>><br>
>> This doesn't currently work, although it does work for the yt repo, I<br>
>> think because we use named branches in that repository.<br>
>><br>
>><br>
>> On Tue, Sep 3, 2013 at 12:00 PM, John ZuHone <<a href="mailto:jzuhone@gmail.com">jzuhone@gmail.com</a>> wrote:<br>
>>><br>
>>> Works fine for me on OS X x86_64.<br>
>>><br>
>>> On my Goddard-controlled Linux x86_64 server, everything worked fine<br>
>>> except Mercurial, which I "conda install"-ed using the yt link, but the<br>
>>> binary had an incompatibility which the glibc that was installed on the<br>
>>> machine. Using pip to install Mercurial (which did it from source) was the<br>
>>> workaround.<br>
>>><br>
>>> On Sep 3, 2013, at 2:54 PM, Matthew Turk <<a href="mailto:matthewturk@gmail.com">matthewturk@gmail.com</a>> wrote:<br>
>>><br>
>>> > Hi all,<br>
>>> ><br>
>>> > Thanks to everybody who has reported back on testing. After some<br>
>>> > talking both offline and on IRC, as well as here, I think we would<br>
>>> > need to do the following things:<br>
>>> ><br>
>>> > * Make a single script that grabs the appropriate distribution of<br>
>>> > miniconda and installs it. Right now I have a mechanism for doing<br>
>>> > this, but it's currently tied to an architecture.<br>
>>> > * Create a mechanism for installing all the packages we need. Nearly<br>
>>> > all are available inside the Continuum repos. What we're hung up on<br>
>>> > is that source installs require a "recipe", and transmitting the<br>
>>> > recipe is where I don't have an idea of what to do.<br>
>>> > * Test this out lots of places<br>
>>> > * Clean up the edges in the (new) install script<br>
>>> > * Move the old install script to maintenance mode<br>
>>> > * Update all documentation to describe this and mothball other<br>
>>> > methods of installation<br>
>>> ><br>
>>> > What would be nice:<br>
>>> ><br>
>>> > * Make available nightly builds of yt on several architectures using<br>
>>> > binstar<br>
>>> > * Utilize more of the packages included in conda elsewhere in yt, now<br>
>>> > that we can!<br>
>>> ><br>
>>> > Here's my current recipe for get_yt.sh:<br>
>>> ><br>
>>> > <a href="http://paste.yt-project.org/show/3843/" target="_blank">http://paste.yt-project.org/show/3843/</a><br>
>>> ><br>
>>> > (The config thing may get switched to include the --system argument,<br>
>>> > to modify the "yt-conda" condarc.) The step that I'm most stuck on is<br>
>>> > getting the yt recipe to people. If we want to make it possible and<br>
>>> > easy to build from source, we need to get the contents of a "conda<br>
>>> > recipe" to people. They can then run "conda build ." in the<br>
>>> > directory. Here are the recipes that we've been playing with:<br>
>>> ><br>
>>> > <a href="https://bitbucket.org/yt_analysis/yt_conda/src" target="_blank">https://bitbucket.org/yt_analysis/yt_conda/src</a><br>
>>> ><br>
>>> > Basically, in get_yt.sh, to do from source instead of from binary we<br>
>>> > need to insert a step at the end that downloads the recipes somehow<br>
>>> > and then cd's into the right directory and builds them. The reason<br>
>>> > this is tricky is that we often need to bootstrap ourselves; we can't<br>
>>> > assume anything exists. We can download the .tar.bz2 of the current<br>
>>> > tip of the repo, but it includes the hash in the directory name that<br>
>>> > it extracts to.<br>
>>> ><br>
>>> > So I think what we need is a mechanism for getting the current state<br>
>>> > of the repo, figuring out the name of the repo's directory, moves into<br>
>>> > it, and then builds. I believe that all/most of this becomes much,<br>
>>> > much easier if hg gets included in Anaconda, which Nathan has<br>
>>> > submitted a PR for. So hopefully that will be taken care of, but<br>
>>> > until that time we can possibly figure something out. I'm not sure<br>
>>> > that we have the resources to continually support binary nightly<br>
>>> > builds in perpetuity for all the architectures that people run on, so<br>
>>> > having source would be awesome. Plus, one of the biggest appeals of<br>
>>> > how we distribute yt is that the source is included; I would very much<br>
>>> > not like to give this up.<br>
>>> ><br>
>>> > Thoughts? Has anyone else tested any of this out?<br>
>>> ><br>
>>> > -Matt<br>
>>> ><br>
>>> > On Tue, Sep 3, 2013 at 1:04 PM, Britton Smith <<a href="mailto:brittonsmith@gmail.com">brittonsmith@gmail.com</a>><br>
>>> > wrote:<br>
>>> >> Hi everyone,<br>
>>> >><br>
>>> >> Sorry for chiming in late. I just moved when this thread began and do<br>
>>> >> not<br>
>>> >> have regular internet access.<br>
>>> >><br>
>>> >> I really like this idea of conda, especially as a package manager that<br>
>>> >> only<br>
>>> >> optionally makes its own edits to your .bashrc. I have always really<br>
>>> >> liked<br>
>>> >> that the install script creates a clean python stack with basically<br>
>>> >> everything a python user needs. I have on occasion suggested it to<br>
>>> >> people<br>
>>> >> just looking to use numpy and matploblib. It looks like conda will<br>
>>> >> continue<br>
>>> >> to provide this nice by-product, so I'm all for it.<br>
>>> >><br>
>>> >> I won't be in a position to help with testing and such for another<br>
>>> >> week or<br>
>>> >> so when I get regular internet access, but I would be glad to do so<br>
>>> >> then.<br>
>>> >><br>
>>> >> Britton<br>
>>> >><br>
>>> >><br>
>>> >> On Fri, Aug 30, 2013 at 9:29 PM, Nathan Goldbaum<br>
>>> >> <<a href="mailto:nathan12343@gmail.com">nathan12343@gmail.com</a>><br>
>>> >> wrote:<br>
>>> >>><br>
>>> >>> Everything should be available now for 64 bit linux and OS X.<br>
>>> >>><br>
>>> >>><br>
>>> >>> On Fri, Aug 30, 2013 at 10:52 AM, Chris Malone<br>
>>> >>> <<a href="mailto:chris.m.malone@gmail.com">chris.m.malone@gmail.com</a>><br>
>>> >>> wrote:<br>
>>> >>>><br>
>>> >>>> Hi Nathan,<br>
>>> >>>><br>
>>> >>>> That appears to work as it built the environment and `conda install<br>
>>> >>>> ...`<br>
>>> >>>> added packages to my environment.<br>
>>> >>>><br>
>>> >>>> One mistake I made was that I originally downloaded the "latest" OS<br>
>>> >>>> X<br>
>>> >>>> build of Miniconda, but that happened to be Miniconda3, which is<br>
>>> >>>> python 3<br>
>>> >>>> based. Trying to build the environment with that yields an error<br>
>>> >>>> regarding<br>
>>> >>>> incompatibility of yt and python3.3, as it should.<br>
>>> >>>><br>
>>> >>>> Chris<br>
>>> >>>><br>
>>> >>>><br>
>>> >>>> On Fri, Aug 30, 2013 at 10:42 AM, Nathan Goldbaum<br>
>>> >>>> <<a href="mailto:nathan12343@gmail.com">nathan12343@gmail.com</a>><br>
>>> >>>> wrote:<br>
>>> >>>>><br>
>>> >>>>> Hey Chris,<br>
>>> >>>>><br>
>>> >>>>> I don't think mercurial is strictly necessary, can you try again<br>
>>> >>>>> without<br>
>>> >>>>> it? I think if Matt uploads a mercurial package for OS X this<br>
>>> >>>>> won't be an<br>
>>> >>>>> issue. I'll send him an updated tarball.<br>
>>> >>>>><br>
>>> >>>>> I submitted a mercurial recipe to conda-recipes yesterday<br>
>>> >>>>> (<a href="https://github.com/ContinuumIO/conda-recipes/pull/14" target="_blank">https://github.com/ContinuumIO/conda-recipes/pull/14</a>) so hopefully<br>
>>> >>>>> a<br>
>>> >>>>> mercurial build will be included in future anaconda releases.<br>
>>> >>>>><br>
>>> >>>>><br>
>>> >>>>> On Fri, Aug 30, 2013 at 10:39 AM, Chris Malone<br>
>>> >>>>> <<a href="mailto:chris.m.malone@gmail.com">chris.m.malone@gmail.com</a>> wrote:<br>
>>> >>>>>><br>
>>> >>>>>> I just tried setting this up on OS X 10.7.5 and failed when<br>
>>> >>>>>> attempting<br>
>>> >>>>>> to create the conda environment due to a missing mercurial<br>
>>> >>>>>> package:<br>
>>> >>>>>><br>
>>> >>>>>> $ conda create -n ytenv -c <a href="http://conda.binstar.org/yt_project" target="_blank">http://conda.binstar.org/yt_project</a> yt<br>
>>> >>>>>> mercurial ipython tornado pyzmq pygments jinja2 sphinx<br>
>>> >>>>>> Error: No packages found matching: mercurial<br>
>>> >>>>>><br>
>>> >>>>>><br>
>>> >>>>>> On Thu, Aug 29, 2013 at 9:01 PM, Nathan Goldbaum<br>
>>> >>>>>> <<a href="mailto:nathan12343@gmail.com">nathan12343@gmail.com</a>> wrote:<br>
>>> >>>>>>><br>
>>> >>>>>>> Yup, please try on OSX as well. If you make sure Matt's binstar<br>
>>> >>>>>>> is in<br>
>>> >>>>>>> your .condarc, you should be able to get yt by doing 'conda<br>
>>> >>>>>>> install yt'.<br>
>>> >>>>>>><br>
>>> >>>>>>> I built the OSX binary on my laptop so I'd appreciate hearing<br>
>>> >>>>>>> about<br>
>>> >>>>>>> issues, particularly if there are issues on older OS X releases.<br>
>>> >>>>>>><br>
>>> >>>>>>> On Thursday, August 29, 2013, Matthew Turk wrote:<br>
>>> >>>>>>>><br>
>>> >>>>>>>> Hi all,<br>
>>> >>>>>>>><br>
>>> >>>>>>>> Thank you for the feedback -- I am glad there is some agreement<br>
>>> >>>>>>>> about<br>
>>> >>>>>>>> possible ways forward, and so I'm happy to try to use this as an<br>
>>> >>>>>>>> opportunity to explore simpler, more reliable methods than the<br>
>>> >>>>>>>> install<br>
>>> >>>>>>>> script.<br>
>>> >>>>>>>><br>
>>> >>>>>>>> This afternoon, I spent a bit of time with Conda, and I think<br>
>>> >>>>>>>> it's<br>
>>> >>>>>>>> quite nice. There are a few rough corners, particularly related<br>
>>> >>>>>>>> to<br>
>>> >>>>>>>> the binstar service, but it's so far pretty great. With<br>
>>> >>>>>>>> Nathan's<br>
>>> >>>>>>>> help, I was able to upload a yt-2.5.5 package for linux x86_64<br>
>>> >>>>>>>> and<br>
>>> >>>>>>>> then install it.<br>
>>> >>>>>>>><br>
>>> >>>>>>>> The workflow that seems to work:<br>
>>> >>>>>>>><br>
>>> >>>>>>>> * Get miniconda: <a href="http://repo.continuum.io/miniconda/index.html" target="_blank">http://repo.continuum.io/miniconda/index.html</a><br>
>>> >>>>>>>> * Run the installer for miniconda<br>
>>> >>>>>>>> * Enter the conda environment and then install yt by doing<br>
>>> >>>>>>>> "conda<br>
>>> >>>>>>>> install yt -c <a href="http://conda.binstar.org/yt_project/" target="_blank">http://conda.binstar.org/yt_project/</a> ".<br>
>>> >>>>>>>><br>
>>> >>>>>>>> I think that this can likely all be stuck into a bash script. A<br>
>>> >>>>>>>> simple, first pass at this is here:<br>
>>> >>>>>>>><br>
>>> >>>>>>>> <a href="http://paste.yt-project.org/show/3833/" target="_blank">http://paste.yt-project.org/show/3833/</a><br>
>>> >>>>>>>><br>
>>> >>>>>>>> This right now only works on Linux x86_64, but getting it to<br>
>>> >>>>>>>> work for<br>
>>> >>>>>>>> other machines won't be too hard. I suspect we will be able to<br>
>>> >>>>>>>> do<br>
>>> >>>>>>>> nightlies very easily as well. If anyone out there has an<br>
>>> >>>>>>>> x86_64<br>
>>> >>>>>>>> machine they wouldn't mind trying it on, that would be very<br>
>>> >>>>>>>> helpful!<br>
>>> >>>>>>>> I did find that once I ran this script, I had to actually<br>
>>> >>>>>>>> prepend the<br>
>>> >>>>>>>> PATH afterwards as well. This means doing:<br>
>>> >>>>>>>><br>
>>> >>>>>>>> export LD_LIBRARY_PATH=$HOME/yt-conda:$LD_LIBRARY_PATH<br>
>>> >>>>>>>> export PATH=$HOME/yt-conda:$PATH<br>
>>> >>>>>>>> source activate ytenv<br>
>>> >>>>>>>><br>
>>> >>>>>>>> At that point, everything was set up and working for me. The<br>
>>> >>>>>>>> miniconda install offers to add paths to .bashrc, but I don't<br>
>>> >>>>>>>> think<br>
>>> >>>>>>>> we<br>
>>> >>>>>>>> should go down that route. That being said, this is also a<br>
>>> >>>>>>>> possible<br>
>>> >>>>>>>> point of friction.<br>
>>> >>>>>>>><br>
>>> >>>>>>>> One nice thing is that this also completely works with the full<br>
>>> >>>>>>>> anaconda; if someone wants everything that is in the anaconda<br>
>>> >>>>>>>> install,<br>
>>> >>>>>>>> they can even simply do "conda install anaconda" from the<br>
>>> >>>>>>>> command<br>
>>> >>>>>>>> line<br>
>>> >>>>>>>> to get it. But the stripped down subset is the default.<br>
>>> >>>>>>>><br>
>>> >>>>>>>> If anyone has a chance to try this out and has feedback, I'd<br>
>>> >>>>>>>> greatly<br>
>>> >>>>>>>> appreciate it! I think Nathan has done something very similar<br>
>>> >>>>>>>> for<br>
>>> >>>>>>>> OSX. I've also put a couple simple conda recipes here:<br>
>>> >>>>>>>> <a href="https://bitbucket.org/yt_analysis/yt_conda" target="_blank">https://bitbucket.org/yt_analysis/yt_conda</a> which we can use as a<br>
>>> >>>>>>>> basis<br>
>>> >>>>>>>> for distributing builds and setting them up on buildbots and the<br>
>>> >>>>>>>> like.<br>
>>> >>>>>>>> I'm pretty optimistic about this.<br>
>>> >>>>>>>><br>
>>> >>>>>>>> -Matt<br>
>>> >>>>>>>><br>
>>> >>>>>>>> On Thu, Aug 29, 2013 at 5:50 PM, Nathan Goldbaum<br>
>>> >>>>>>>> <<a href="mailto:nathan12343@gmail.com">nathan12343@gmail.com</a>> wrote:<br>
>>> >>>>>>>>> I think to get everything working in a sustainable fashion, we<br>
>>> >>>>>>>>> would need<br>
>>> >>>>>>>>> buildbots for all platform combinations that we want to<br>
>>> >>>>>>>>> support, so<br>
>>> >>>>>>>>> all<br>
>>> >>>>>>>>> permutations of the (32/64 bit, linux / OS X / windows,<br>
>>> >>>>>>>>> py27/py3.3) tuple.<br>
>>> >>>>>>>>> At the moment anaconda seems to support 32 and 64 bit linux, 64<br>
>>> >>>>>>>>> bit<br>
>>> >>>>>>>>> OS X<br>
>>> >>>>>>>>> (not totally clear if OS X version matters), and 32 and 64 bit<br>
>>> >>>>>>>>> windows.<br>
>>> >>>>>>>>><br>
>>> >>>>>>>>> Another option is to rely on conda build, which compiles<br>
>>> >>>>>>>>> everything<br>
>>> >>>>>>>>> from<br>
>>> >>>>>>>>> source.<br>
>>> >>>>>>>>><br>
>>> >>>>>>>>><br>
>>> >>>>>>>>> On Thu, Aug 29, 2013 at 2:45 PM, Stephen Skory <<a href="mailto:s@skory.us">s@skory.us</a>><br>
>>> >>>>>>>>> wrote:<br>
>>> >>>>>>>>>><br>
>>> >>>>>>>>>> Hi all,<br>
>>> >>>>>>>>>><br>
>>> >>>>>>>>>> I have less of a skin in this than I used to, but I'd like to<br>
>>> >>>>>>>>>> raise<br>
>>> >>>>>>>>>> the issue of Windows & package managers. For example, Anaconda<br>
>>> >>>>>>>>>> is<br>
>>> >>>>>>>>>> available for Windows - would that mean that yt might "just<br>
>>> >>>>>>>>>> work"<br>
>>> >>>>>>>>>> on<br>
>>> >>>>>>>>>> Windows? Or the opposite, and it would require a great deal of<br>
>>> >>>>>>>>>> effort<br>
>>> >>>>>>>>>> to get all the various things we expect to be .so's to work as<br>
>>> >>>>>>>>>> .dll's<br>
>>> >>>>>>>>>> (such as the Cython helpers or halo-finding stuff)?<br>
>>> >>>>>>>>>><br>
>>> >>>>>>>>>> I don't know the answers to these questions, but I think it's<br>
>>> >>>>>>>>>> worth<br>
>>> >>>>>>>>>> thinking about.<br>
>>> >>>>>>>>>><br>
>>> >>>>>>>>>> --<br>
>>> >>>>>>>>>> Stephen Skory<br>
>>> >>>>>>>>>> <a href="mailto:s@skory.us">s@skory.us</a><br>
>>> >>>>>>>>>> <a href="http://stephenskory.com/" target="_blank">http://stephenskory.com/</a><br>
>>> >>>>>>>>>> <a href="tel:510.621.3687" value="+15106213687">510.621.3687</a> (google voice)<br>
>>> >>>>>>>>>> _______________________________________________<br>
>>> >>>>>>>>>> yt-dev mailing list<br>
>>> >>>>>>>>>> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> >>>>>>>>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>> >>>>>>>>><br>
>>> >>>>>>>>><br>
>>> >>>>>>>>><br>
>>> >>>>>>>>> _______________________________________________<br>
>>> >>>>>>>>> yt-dev mailing list<br>
>>> >>>>>>>>> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> >>>>>>>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>> >>>>>>>>><br>
>>> >>>>>>>> _______________________________________________<br>
>>> >>>>>>>> yt-dev mailing list<br>
>>> >>>>>>>> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> >>>>>>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>> >>>>>>><br>
>>> >>>>>>><br>
>>> >>>>>>> _______________________________________________<br>
>>> >>>>>>> yt-dev mailing list<br>
>>> >>>>>>> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> >>>>>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>> >>>>>>><br>
>>> >>>>>><br>
>>> >>>>>><br>
>>> >>>>>> _______________________________________________<br>
>>> >>>>>> yt-dev mailing list<br>
>>> >>>>>> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> >>>>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>> >>>>>><br>
>>> >>>>><br>
>>> >>>>><br>
>>> >>>>> _______________________________________________<br>
>>> >>>>> yt-dev mailing list<br>
>>> >>>>> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> >>>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>> >>>>><br>
>>> >>>><br>
>>> >>>><br>
>>> >>>> _______________________________________________<br>
>>> >>>> yt-dev mailing list<br>
>>> >>>> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> >>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>> >>>><br>
>>> >>><br>
>>> >>><br>
>>> >>> _______________________________________________<br>
>>> >>> yt-dev mailing list<br>
>>> >>> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> >>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>> >>><br>
>>> >><br>
>>> >><br>
>>> >> _______________________________________________<br>
>>> >> yt-dev mailing list<br>
>>> >> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> >> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>> >><br>
>>> > _______________________________________________<br>
>>> > yt-dev mailing list<br>
>>> > <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> > <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>><br>
>>> _______________________________________________<br>
>>> yt-dev mailing list<br>
>>> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>><br>
>><br>
>> _______________________________________________<br>
>> yt-dev mailing list<br>
>> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> yt-dev mailing list<br>
>> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> yt-dev mailing list<br>
> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
><br>
_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
</div></div></blockquote></div><br></div>