kenneth_reitz

Thanks for the feedback, integrated w3lib!

<base> tag is now implemented as well. Thanks for bringing that to my attention — I wasn't aware of it!

I addressed most of your issues, like not using urlparse in the latest release.

With libraries like these, it's all about getting the API right first, them optimizing for perfection second. :)

GPL dependency removed.

All of these improvements I'd like to be made to the software. It's all about getting a nice API in place first, then making it perfect second.

I consider it a nice-to-have, but we can definitely remove it if deemed unnecessary. Want to open an issue about it?

updated :)

Looks like there's still some room for improvement though!

That bug has been fixed, but the docs hadn't been. Fixed now :)

It wasn't at first, actually. It was originally a wrapper around urllib2 — Andrey and I collabed early on in both project's histories to make them what they are today.

Very different use cases, imo. MechanicalSoup emulates a web browser experience. This is more for scraping.

Aaron Swartz

My thoughts exactly :)

See also: pipenv :)

http://docs.pipenv.org/en/latest/

Very different tools, but they cover the same surface area, in spots.

I'm bipolar!

I wrote it by hand with tufte-css :)

I love Swagger.yaml, and considered it for this project, but it's small enough to do by hand...

For example, all the queries on the homepage are live results :)

I made this this week: https://coinbin.org/

In a similar vein.

The data was stale, it turns out, for some coins — issue fixed now.

Yes.

I like this idea! Want to add a PR?

Operator Mono! https://www.kennethreitz.org/essays/test-driving-a-200-progr...

coming soon, hopefully via pull request!

Also `pipenv install -r requirements.txt` is supported, for importing.

Fish support was just added!

Check out https://github.com/pypa/pipfile for more info. The format is TOML. It is mainly intended for deployments (e.g. web applications)

Do I look unhappy at conferences or something?

that's why there's `maya.when('yesterday', timezone='US/Eastern')` :)

you'd be surprised, the amount of headache-inducing code that timezones can cause, especially when dealing with servers with different locales than your development machine when doing timezone algebra.

This API avoids that problem entirely.

The problem is that it can be used in both a deterministic and non-deterministic way (no version-specifiers specified, not all sub-dependencies listed). People want the best of both worlds.

This facilitates that.

Some speculate that it already has.

Oh cool, I didn't know about this!