<p dir="ltr">Matt, you're now officially the Ferdinand Magellan of the exploration. Let us know how it goes.</p>
<br><div class="gmail_quote"><div dir="ltr">On Mon, Sep 18, 2017, 7:47 PM Sam Skillman <<a href="mailto:samskillman@gmail.com">samskillman@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">libconf, while being significantly more complicated than pyparselibconfig, seems also far superior. +1 from me for jettisoning pyparselibconfig.</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 18, 2017 at 6:21 PM, Sam Skillman <span dir="ltr"><<a href="mailto:samskillman@gmail.com" target="_blank">samskillman@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Oh, now I see that this was just a ploy to get me to contribute again! Just when you think you're out.... <br><br>But seriously, happy to help if desired, but also happy to not get in the way and delay getting things done. Hope you all are doing well.</div><div class="m_1741180001697303720HOEnZb"><div class="m_1741180001697303720h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 18, 2017 at 6:04 PM, 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">Ooh, I change my vote to exploring this option first.<br>
<div class="m_1741180001697303720m_-4894198519582177820HOEnZb"><div class="m_1741180001697303720m_-4894198519582177820h5"><br>
On Mon, Sep 18, 2017 at 7:03 PM, Sam Skillman <<a href="mailto:samskillman@gmail.com" target="_blank">samskillman@gmail.com</a>> wrote:<br>
> As the original author of pyparselibconfig, I release all obligations of<br>
> keeping it around. I have a *very* vague memory that I wrote it because the<br>
> other options at the time were either painful to install, bloated, or<br>
> possibly both. My guess is that it worked for some file associated with<br>
> Enzo-3, which may or may not have been libconf feature complete. If there<br>
> was still interest in supporting pyparselibconfig, I'd be open to taking an<br>
> example cfg file and fumbling around a bit to see if I can get it to work.<br>
><br>
> Cheers,<br>
> Sam<br>
><br>
> On Mon, Sep 18, 2017 at 2:48 PM, Britton Smith <<a href="mailto:brittonsmith@gmail.com" target="_blank">brittonsmith@gmail.com</a>><br>
> wrote:<br>
>><br>
>> Matt, you are also correct. Enzo-P ingests a non-libconfig style format,<br>
>> but outputs in both this native format and normal libconfig. It would also<br>
>> be great to be able to parse the native format, but that would need to be<br>
>> written from scratch.<br>
>><br>
>> On Mon, Sep 18, 2017 at 1:43 PM, Matthew Turk <<a href="mailto:matthewturk@gmail.com" target="_blank">matthewturk@gmail.com</a>><br>
>> wrote:<br>
>>><br>
>>> I'm okay with this.<br>
>>><br>
>>> I thought Enzo-P used a non-libconfig style (something about equations<br>
>>> outside of quotation marks) but it sounds like that's no longer accurate.<br>
>>><br>
>>> On Sep 18, 2017 3:38 PM, "Britton Smith" <<a href="mailto:brittonsmith@gmail.com" target="_blank">brittonsmith@gmail.com</a>> wrote:<br>
>>>><br>
>>>> Hi all,<br>
>>>><br>
>>>> I am working on a new yt frontend for the Enzo-P code. Enzo-P outputs<br>
>>>> runtime parameters in a libconfig format and I am looking for a reliable<br>
>>>> package to read this.<br>
>>>><br>
>>>> yt has a libconfig-style reader in yt/utilities/pyparselibconfig, but it<br>
>>>> does not seem to parse Enzo-P parameter files correctly. I have tried a few<br>
>>>> other python libconfig parsers that do parse them correctly, so I believe<br>
>>>> the problem is with the yt module. For what it's worth, the only use of<br>
>>>> yt's libconfig parser is in the Enzo frontend for a certain style of<br>
>>>> Enzo-3.0 data, but it doesn't look like this is being tested, nor do we host<br>
>>>> any sample data of this format.<br>
>>>><br>
>>>> I have a PR open for the Enzo-P frontend here that makes use of an<br>
>>>> external package, called libconf. I've implemented this as an on-demand<br>
>>>> import, so it will only be required if you're actually loading Enzo-P data.<br>
>>>><br>
>>>> The pros for libconf are that it's pure python, pip installable, has a<br>
>>>> permissive MIT license, and works in both python 2 and 3. The con is of<br>
>>>> course that this adds a new dependency. Personally, I would prefer not<br>
>>>> having to maintain our own module to do this, but I'm open to other<br>
>>>> opinions.<br>
>>>><br>
>>>> What are people's thoughts on adding this dependency?<br>
>>>><br>
>>>> Britton<br>
>>>><br>
>>>> _______________________________________________<br>
>>>> yt-dev mailing list<br>
>>>> <a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
>>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" rel="noreferrer" 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" target="_blank">yt-dev@lists.spacepope.org</a><br>
>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" rel="noreferrer" 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" target="_blank">yt-dev@lists.spacepope.org</a><br>
>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" rel="noreferrer" 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" target="_blank">yt-dev@lists.spacepope.org</a><br>
> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" rel="noreferrer" 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" target="_blank">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" rel="noreferrer" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" rel="noreferrer" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
</blockquote></div>