-
Notifications
You must be signed in to change notification settings - Fork 200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
decouple.Csv() makes raw strings not-raw, incorrectly #102
Comments
That's an interesting problem. Sure the inconsistency should be solved. Don't know yet what could be done with CSV. Can you provide a PR with the desired failing tests and the expected results? This would make easy for me to figure out what to do. |
I will see what I can do to help! |
Hi, I created #103 to tackle this bug. Please let me know if there's anything else I can do to help. |
Hi, any chance of getting traction on this issue? I think the code is all ready to go in #103. |
Yes. But this is not an CSV issue. It's more general. I'll need to write the proper tests to make sure all the corners are covered. |
The django-cors-headers middleware has two ways to control
Access-Control-Allow-Origin
. One of them is via a regular expressionCORS_ALLOWED_ORIGIN_REGEXES
, which is a list of strings that are regular expressions. Unfortunately, we've been struggling to use a regex liker"^https://\w+\.example\.com$"
. That is, we triedand set the value in the environment, and that didn't work because…
which is not the same regular expression we entered. Honestly, the other side of our problem is helmfile, which makes it difficult to set environment variables with backslashes in them, but we thought at least the default in pure python should work, and would be worth reporting.
If you don't use
Csv()
, the raw string behaves as expected:The text was updated successfully, but these errors were encountered: