Closed matthewhegarty closed 2 years ago
@claudep Is it possible we could get a new release with this fix in? We would need it for our forthcoming v3 release of django-import-export
. I also notice that there was a build failure. Could you re-run the job to test whether it is something we need to fix?
Yes, it's about time for a release. We could wait a day or two to see if we can get https://github.com/jazzband/tablib/pull/516 in?
What's your schedule for django-import-export
?
I don't want to delay if you're ready to go now, we can always release this now and make a new release when that's ready, it's pretty easy to release with the automation.
The build is too old to restart, but here it is passing on my fork:
https://github.com/hugovk/tablib/actions/runs/2076613414
And here's a PR to add a button to allow us to manually trigger builds in the future: https://github.com/jazzband/tablib/pull/519.
What's your schedule for django-import-export?
No rush, this is for our major release which has been pending for a while, so we can certainly wait until you are ready.
Released in 3.2.1! 🚀
Hi I'm testing some changes on
django-import-export
and I notice an issue with LF endings for csv data, which was the format on older mac os distributions.This can be fixed by adding the 'newline' kwarg to
normalize_input()
: