Log file Viewer

[08:01:57] <JayFK> is "package==foo\t\t# some comment" considered valid in a requirements file? pip has no problems to parse this, but setuptools parse_requirements is looking for a ' #' in the line and won't parse it: https://github.com/pypa/setuptools/blob/master/pkg_resources/__init__.py#L2775

[10:00:25] <dstufft> JayFK: setuptools doesn't support comments at all afaik, setuptools expects this stuff to be in a Python file as a Python string, so it makes more sense to have the comment outside of the string as a regular Python comment

[15:39:20] <agronholm> dstufft: would you be open to the idea of upgrading that thing to yaml 1.2 compliance?

[15:39:41] <agronholm> that way it'd be a 100% compatible superset to JSON.

[15:40:57] <dstufft> agronholm: in abstract? I have no problem upgrading it to YAML 1.2. My goals right now are to clean up the code and get it running single source py2 and py3

[15:42:00] <agronholm> dstufft: sounds good!

[15:42:55] <agronholm> I'm too tired to help right now but I'll take another look at what you have when I've had some shuteye

[16:47:28] <dstufft> agronholm: https://github.com/dstufft/yaml/pull/3

[16:47:49] <dstufft> only took me two hours

[16:48:06] <dstufft> probably lost support for old style calsses, but I plan on killing the !!python thing anyways

[16:56:32] <agronholm> dstufft: why all those __future__ imports on separate lines?

[16:57:15] <dstufft> agronholm: *shrug*, just how I've always done __future__ imports

[16:57:49] <agronholm> but other modules you import normally, like from functools import reduce, wraps?

[16:57:57] <dstufft> yea

[16:58:04] <dstufft> don't ask me why :D

[16:58:28] <agronholm> other than that, looks good so far

[19:28:03] <sanguisdex> how do I tell a requirement's requirement that I want to install install a forked version of the required requirement? (as in DesiredApp-> Requirement -> forkedRequirment