mirror of
https://github.com/modoboa/modoboa.git
synced 2026-04-26 01:16:01 +03:00
[GH-ISSUE #1430] CSV import broken #1133
Labels
No labels
bug
bug
dependencies
design
documentation
duplicate
enhancement
enhancement
enhancement
feedback-needed
help-needed
help-needed
installer
invalid
looking-for-sponsors
modoboa-contacts
new-ui
new-ui
pr
pull-request
pyconfr
python
question
security
stale
webmail
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/modoboa-modoboa#1133
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @almereyda on GitHub (Mar 8, 2018).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/1430
Impacted versions
Steps to reproduce
Run an email import from a CSV formed after http://modoboa.readthedocs.io/en/latest/moving.html#using-csv-files, i.e. one that worked before.
Current behavior
It feels #1342 was a bit of a too quick shot at #1312 and may need further iterations to constrain the import a little more.
Manually passing
dialect='excel'by editing_import.pydid not help, either.github.com/modoboa/modoboa@83d0564c27/modoboa/admin/management/commands/subcommands/_import.py (L57)The original error may reside around https://github.com/ryanhiebert/backports.csv/blob/master/src/backports/csv.py#L230
Unfortunately the upstream package does not provide a test suite.
Expected behavior
The import completes successfully.
@ghost commented on GitHub (Mar 9, 2018):
Well Line 232 of csv.py destroys any useful error message and replaces it with
Invalid dialect parameters.I don't think this is a utf8 problem, I think
options["sepchar"]is either None or an instance ofstrinstead ofunicode, I'll need to do some testing in the morning.Can you try running
@almereyda commented on GitHub (Mar 9, 2018):
Thanks for the introspection.
The escaped SEPCHAR yields the very same error.
On 9 March 2018 at 01:22, Andrew Fyfe notifications@github.com wrote:
@tonioo commented on GitHub (Oct 1, 2018):
@almereyda Is it still happening?
@almereyda commented on GitHub (Oct 2, 2018):
We didn't have a chance to test it again, but will have next week, Thu 11th
of October.
On Mon, 1 Oct 2018 at 13:12, Antoine Nguyen notifications@github.com
wrote:
@tonioo commented on GitHub (Oct 18, 2018):
@almereyda Any news?
@augustodv commented on GitHub (Jun 24, 2019):
hello, i have de same error and test all but the error persist.
@Spitfireap commented on GitHub (Jul 15, 2024):
Should be fixed by #3039. Please open a new ticket if it still shows up.