[ckan-dev] requests version change
Adrià Mercader
adria.mercader at okfn.org
Thu Dec 6 15:43:45 UTC 2012
I think it's worth spending some time upgrading the extensions too. We
can do it on the process on making sure they work fine with 2.0 (qa
and archiver should be supported)
Adrià
On 6 December 2012 15:08, John Glover <john.glover at okfn.org> wrote:
> I'm pretty sure we added the specific version because the Requests API
> changed slightly in later versions and broke the extensions. We should
> really update the extensions though.
>
> John G
>
>
> On 6 December 2012 14:05, Toby Dacre <toby.okfn at gmail.com> wrote:
>>
>> some extensions seem to require requests==0.6.4 and we have upgraded the
>> version in core. There is something odd with our tests that trigger this
>> even if the extensions appear not to be being used.
>>
>> qa and archiver seem to be affected
>>
>> this causes paster db init to fail so it seems important. We could fix it
>> either in model.Repository.init_db() or in lib.celery_app
>>
>> what do people think? Also should we be adding these requires for
>> extensions? maybe request>=0.6.4 is better than requires==6.4 unless we know
>> a future version is problematic?
>>
>> Toby
>>
>> _______________________________________________
>> ckan-dev mailing list
>> ckan-dev at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/ckan-dev
>> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev
>>
>
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev
>
More information about the ckan-dev
mailing list