Py3

Does what it says on the tin.
BTW, IIRC the reason this change is in this change set is that some deps
introduced py3 support later than we had pinned them.
On Jul 3, 2014 11:30 AM, randall@bleeds.info wrote:

I'm torn.

On one hand, pins are good when they prevent breakage.

On the other, I like to be optimistic about forward compatibility.

If breakage happens, applications can always pin second level dependencies
until we hear about it and release.

But application developers are stuck until we make a release if they need a
newer version of something that we pin.

So the best guidance I can come up with hinges on whether this is a library
or an application primarily. And that's a weak guide anyway I think.

Any resources you know for research here send em my way. I'll do some
googling.
On Jul 3, 2014 1:26 AM, "Nick Stenning" <notifications@github.com> wrote:

In setup.py:

> @@ -2,10 +2,11 @@
>  import os
>
>  requires = [
> -    'Flask==0.9',
> +    'Flask',

I'd need to be convinced that unpinning these is the right thing to do.

—
Reply to this email directly or view it on GitHub
<https://github.com/openannotation/annotator-store/pull/72/files#r14502175>.