Hi! I discover this problem start with Django 2.1, Django 2.0.13 still
working good. I'm reading the changes on Django 2.1 whom can cause this
problem. Thanks for the ideas!
On Wednesday, October 16, 2019 at 4:35:36 PM UTC-3, Boris Romero wrote:
>
> Thanks again for the answer. I believe the pro
Thanks again for the answer. I believe the problem is related with unicode
changes between python versions, but I think it's a problem from any
library or dependency used at the app, whom is not working properly,
because with the same python version the problem appears and dissapears
using diff
okay, but it's even harder to guess what is a problem there without ability
to see relevant code pieces. btw, you may want to check this
https://www.geeksforgeeks.org/important-differences-between-python-2-x-and-python-3-x-with-examples/#Unicode
as
you most probably had to migrate python as wel
Thanks for the answer Lemme! As I said, my problems appear exactly when I
update django from 1.11 to django 2.2.x. With this change a lot of
libraries need to update, and now I was trying to remove some of them and
proving if they are the reason of this strange behavior. Before update
django, a
it's really hard to help here without understanding whats going on there.
when i ask for example I meant not only piece of page screenshot to see
what you mean, but whole stack of how you pass data in a view and how you
render it in a template
On Tuesday, October 15, 2019 at 9:31:26 PM UTC+3, B
Any help or ideas? Thanks!
On Thursday, October 10, 2019 at 12:15:42 PM UTC-3, Boris Romero wrote:
>
> Hi! Yes, it's reproducing when I run it locally, but with DEBUG=FALSE and
> with nginx and uwsgi. And no, it's not a database encoding problem, it just
> involves the templates, because the sam
Hi! Yes, it's reproducing when I run it locally, but with DEBUG=FALSE and
with nginx and uwsgi. And no, it's not a database encoding problem, it just
involves the templates, because the same database, with diferents instances
of the app (with the upload and without it) not make any differences.
so, it's not reproducing when you run it locally?
also, can you provide an example of string where you have "strange"
character? most probably you store it in database.
On Thursday, October 10, 2019 at 1:48:52 AM UTC+3, Boris Romero wrote:
>
> Hi!
>
> I recently update Django from 1.11 to 2.2.6
8 matches
Mail list logo
