ThrawnCA
ThrawnCA
> On detecting types in general use, I'm not keen to rely too much on the messytables load because it does a tiresome conversion to chunks of JSON and then...
Is this still needed under Python 3? If so, @metaodi merge conflicts will need to be resolved.
I don't understand what situation would fail to have a format.
> Some ckan admin's may have decided to drop that field on their servers. And still run XLoader, which relies on the format field to know whether it should try...
> Your thoughts? I suppose it's harmless, it just seems very odd for anyone to need this null-check.
This isn't the only extension that will need such a token; archiver, qa, harvest, validation, etc, will all need something similar. Should there be a more generic key name, something...
> I am currently facing similar issues did you ever get this resolved? We're running this without problems, but instead of putting the token directly in the file, we're injecting...
What version of XLoader are you running?
This looks good to me, but @OriHoch can you resolve the merge conflict?
> @ThrawnCA do you have a pypi account? I don't, no.