A picturesque authentication problem ONLY in Google Chrome

[Rogerio Carrasqueira]

Hello All!

All good? I'm running an application in Django 1.4.22 and some days I'm
facing some difficulties for my users to access the restricted area of my
site. It so happens that I have the site running on the main domain
www.dominio.com.br and the restricted area on app.dominio.com.br, both
running on https, and so far everything is fine.

When the user tries to access the restricted area thru the main domain, he
enters the site www.dominio.com.br and clicks on a link that redirects to
the restricted area in the subdomain app.dominio.com.br, but he cannot log
in, he it puts the username and password and returns to the initial login
page, and it does not authenticate.

After some tests, I verified that if I go to Chrome's privacy settings, I
can delete the cookie for the domain in question, after the removal of
domain cookie information and if the user accesses directly via
app.domain.com.br, without going through the main site www.dominio.com.br,
can log in successfully. Now, if you go through the main site afterwards,
you can no longer log in to the restricted area, you must delete the cookie
again in the Google Chrome settings.

In other browsers this problem does not happen, including in other browsers
of the Chromiun family, such as Brave, Vivaldi and even Micro$oft's own.

Has anyone gone through a similar problem?

Awaiting help from a kind soul

Cheers!

Rogério Carrasqueira

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CACX1ULQ4kMb%2BfdrkfZg0KvBUyfha6zbNDU1u1Grg9cFP_gfR9g%40mail.gmail.com.

Re: how to convert to Django 3 or 4

[Rogério Carrasqueira]

Hey Steven!

Thanks for this information, do you have tried it before? I would like to 
move from 1.4 to lastest, do you think that is it possible?

Thanks

Em quarta-feira, 7 de junho de 2023 às 11:52:35 UTC-3, Steven Mapes 
escreveu:

> I'd suggest looking into using Adam Johnson's Django-Upgrade told -
> https://github.com/adamchainz/django-upgrade it will help you move 
> between versions
>
> On Tuesday, 6 June 2023 at 15:24:36 UTC+1 Paul Haguet wrote:
>
>> There is a lot of function who can change. 
>>
>> https://docs.djangoproject.com/en/4.2/releases/4.0/
>>
>> All the function declared as deprecated into Django 3 has been removed 
>> into Django 4. In the deprecated section of django 3 new functions names 
>> are systematically indicated. So just search the function under their old 
>> name and replace them with their new name. The 2 links below give the list.
>>
>>
>> https://docs.djangoproject.com/en/4.2/releases/3.0/#deprecated-features-3-0
>>
>> https://docs.djangoproject.com/en/4.2/releases/3.1/#deprecated-features-3-1
>>
>> Le samedi 3 juin 2023 à 10:10:31 UTC+2, Shams Ulhaq a écrit :
>>
>>> Just need to change url import 
>>>
>>> from django.urls import include, re_path as url
>>>
>>>
>>> On Sat, 3 Jun 2023, 12:32 David Nugent,  wrote:
>>>
 nppe url is obsolete and removed in 4.x.

 You can use re_path, which is a kind of replacement but even then you 
 will need to adjust the regex in many cases.

 The best approach is to understand what the url() is doing, and 
 replicate the same using path(). Once you do, the conversions should be 
 more or less straight-forward. Instead of regex you use labelled patterns 
 making for more comprehensible path lines. For complex regex expressions 
 you may need to define custom matches - or "converters" - that enforce 
 specific patterns allowing you to restrict input and improve matching. 
 This 
 is one area that Django has improved really well over time.

 But, like I said, don't try to replace this file wholesale. Instead of 
 converting it and doing error-fix-error-fix ad infinitun, re-implement 
 things as you enable parts of the app you have successfully ported. While 
 re_path may be a fallback, try to re-implement as path() expressions and 
 you'll be better in the long run.


 On Sat, Jun 3, 2023 at 11:59 AM Muhammad Juwaini Abdul Rahman <
 juw...@gmail.com> wrote:

> I think Django 4 still have backward compatibility with `url` 
> although `path` is preferable.
>
> You can try to `runserver` in your local, upgrade your django version 
> in your virtualenv to version 4 and troubleshoot the error messages (if 
> any) one by one.
>
> On Sat, 3 Jun 2023 at 05:20, john fabiani  
> wrote:
>
>> Hi everyone,
>>
>> I am tasked with updating/upgrading a very old Django web site - I 
>> believe it is 1.7.  I need convert and need what is required.
>> Thanks in advance.
>>
>>
>> I need to convert the following:
>>
>> from django.conf.urls import patterns, include, url
>> from django.contrib import admin
>> from django.conf import settings
>> from django.conf.urls.static import static
>>
>> urlpatterns = patterns('',
>> # Examples:
>> url(r'reg4/$', 'register.views.reg4', name='reg4'),
>> url(r'reg3/$', 'register.views.reg3', name='reg3'),
>> url(r'reg2/$', 'register.views.reg2', name='reg2'),
>> #url(r'reg1/$', 'register.views.reg1', name='reg1'),
>> url(r'reg1/$', 'register.views.reg1', name='reg1'),
>> #url(r'^$', 'register.views.home', name='home'),
>> url(r'reg/$', 'register.views.home', name='home'),
>> url(r'get_courts/(\d+)$', 'register.views.get_courts', 
>> name='get_courts'),
>> url(r'get_courses/(\d+)$', 'register.views.get_courses', 
>> name='get_courses'),
>> url(r'autoschedule/', 'register.views.autoschedule', 
>> name='autoschedule'),
>> url(r'get_cities/(\d+)$', 'register.views.get_cities', 
>> name='get_cities'),
>> url(r'get_classes/(\d+)$', 'register.views.get_classes', 
>> name='get_classes'),
>> url(r'get_cities2/(\d+)/(\d+)/$', 'register.views.get_cities2', 
>> name='get_cities2'),
>> url(r'get_classes2/(\d+)/(\d+)/$', 'register.views.get_classes2', 
>> name='get_classes2'),
>> url(r'rejected/$', 'register.views.rejected', name='rejected'),
>> url(r'finished/$', 'register.views.finished', name='finished'),
>> 
>> ##url(r'^$', 'profiles.views.home', name='home'),
>> #url(r'^contact/$', 'register.views.home', name='contact'),
>> #url(r'^about/$', 'register.views.about', name='about'),
>> #url(r'^profile/$', 'register.views.user_profile', 
>> name='profile'),
>> #url(r'^checkout/$', 'checkout.views.checkout', 
>> name='checkout'),

CSV file

[Percy Masekwameng]

Hi

I have web app survey that collect data and generate a CSV file,
I'm using railway to deploy my web app, running on 8GB RAM and each time I
generate a file, the server goes down and display "Application failed to
respond" the database table has over 2k records
Is there any way to improve the performance so that I can be able to
download large dataset from the web app?

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CANfc-pBoutR0kD%3DcqwRHGSQ8gac%2B_YLMyCQoFK--%3DD54TZpotA%40mail.gmail.com.

Re: A picturesque authentication problem ONLY in Google Chrome

[Fabio C. Barrionuevo da Luz]

Try to define the SESSION_COOKIE_DOMAIN on your settings.py

SESSION_COOKIE_DOMAIN=".dominio.com.br"

https://docs.djangoproject.com/en/4.2/ref/settings/#session-cookie-domain
https://django.readthedocs.io/en/1.4.X/ref/settings.html#session-cookie-domain

That said, Django 1.4.22 was released 8 years ago, and most likely, there
were a lot of fixes between Django 1.4 and 4.2 LTS, including several
security fixes for major flaws, so even if you manage to solve this
particular problem, perhaps you should consider starting planning to port
this system to newer versions of Python and Django.

If you need help with this, Labcodes can help you in migrating and
structure your project to be more maintainable in the long term.

You can contact us by *contact at labcodes.com.br *
and mention my name.





Em qui., 8 de jun. de 2023 às 15:48, Rogerio Carrasqueira <
rogerio.carrasque...@gmail.com> escreveu:

> Hello All!
>
> All good? I'm running an application in Django 1.4.22 and some days I'm
> facing some difficulties for my users to access the restricted area of my
> site. It so happens that I have the site running on the main domain
> www.dominio.com.br and the restricted area on app.dominio.com.br, both
> running on https, and so far everything is fine.
>
> When the user tries to access the restricted area thru the main domain, he
> enters the site www.dominio.com.br and clicks on a link that redirects to
> the restricted area in the subdomain app.dominio.com.br, but he cannot
> log in, he it puts the username and password and returns to the initial
> login page, and it does not authenticate.
>
> After some tests, I verified that if I go to Chrome's privacy settings, I
> can delete the cookie for the domain in question, after the removal of
> domain cookie information and if the user accesses directly via
> app.domain.com.br, without going through the main site www.dominio.com.br,
> can log in successfully. Now, if you go through the main site afterwards,
> you can no longer log in to the restricted area, you must delete the cookie
> again in the Google Chrome settings.
>
> In other browsers this problem does not happen, including in other
> browsers of the Chromiun family, such as Brave, Vivaldi and even
> Micro$oft's own.
>
> Has anyone gone through a similar problem?
>
> Awaiting help from a kind soul
>
> Cheers!
>
> Rogério Carrasqueira
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CACX1ULQ4kMb%2BfdrkfZg0KvBUyfha6zbNDU1u1Grg9cFP_gfR9g%40mail.gmail.com
> 
> .
>


-- 
Fábio C. Barrionuevo da Luz
Palmas - Tocantins - Brasil - América do Sul

http://pythonclub.com.br/

Blog colaborativo sobre Python e tecnologias Relacionadas, mantido
totalmente no https://github.com/pythonclub/pythonclub.github.io .

Todos são livres para publicar. É só fazer fork, escrever sua postagem e
mandar o pull-request. Leia mais sobre como publicar em README.md e
contributing.md.
Regra básica de postagem:
"Você" acha interessante? É útil para "você"? Pode ser utilizado com Python
ou é útil para quem usa Python? Está esperando o que? Publica logo, que
estou louco para ler...

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAPVjvMZuZFjbUg0aM38tzP3Yz9FXsFjhVnJfEGFdK5WVBNa0zg%40mail.gmail.com.

Re: A picturesque authentication problem ONLY in Google Chrome

[Rogério Carrasqueira]

Hello Fabio,

Thanks for you reply, this must be considered on both sites or only in 
subdomain?

Thanks again!

Em quinta-feira, 8 de junho de 2023 às 16:14:37 UTC-3, Fabio C. Barrionuevo 
da Luz escreveu:

> Try to define the SESSION_COOKIE_DOMAIN on your settings.py
>
> SESSION_COOKIE_DOMAIN=".dominio.com.br"
>
> https://docs.djangoproject.com/en/4.2/ref/settings/#session-cookie-domain
>
> https://django.readthedocs.io/en/1.4.X/ref/settings.html#session-cookie-domain
>
> That said, Django 1.4.22 was released 8 years ago, and most likely, there 
> were a lot of fixes between Django 1.4 and 4.2 LTS, including several 
> security fixes for major flaws, so even if you manage to solve this 
> particular problem, perhaps you should consider starting planning to port 
> this system to newer versions of Python and Django.
>
> If you need help with this, Labcodes can help you in migrating and 
> structure your project to be more maintainable in the long term.
>
> You can contact us by *contact at labcodes.com.br 
> * and mention my name.
>
>
>
>
>
> Em qui., 8 de jun. de 2023 às 15:48, Rogerio Carrasqueira <
> rogerio.ca...@gmail.com> escreveu:
>
>> Hello All!
>>
>> All good? I'm running an application in Django 1.4.22 and some days I'm 
>> facing some difficulties for my users to access the restricted area of my 
>> site. It so happens that I have the site running on the main domain 
>> www.dominio.com.br and the restricted area on app.dominio.com.br, both 
>> running on https, and so far everything is fine.
>>
>> When the user tries to access the restricted area thru the main domain, 
>> he enters the site www.dominio.com.br and clicks on a link that 
>> redirects to the restricted area in the subdomain app.dominio.com.br, 
>> but he cannot log in, he it puts the username and password and returns to 
>> the initial login page, and it does not authenticate.
>>
>> After some tests, I verified that if I go to Chrome's privacy settings, I 
>> can delete the cookie for the domain in question, after the removal of 
>> domain cookie information and if the user accesses directly via 
>> app.domain.com.br, without going through the main site www.dominio.com.br, 
>> can log in successfully. Now, if you go through the main site afterwards, 
>> you can no longer log in to the restricted area, you must delete the cookie 
>> again in the Google Chrome settings.
>>
>> In other browsers this problem does not happen, including in other 
>> browsers of the Chromiun family, such as Brave, Vivaldi and even 
>> Micro$oft's own.
>>
>> Has anyone gone through a similar problem?
>>
>> Awaiting help from a kind soul
>>
>> Cheers!
>>
>> Rogério Carrasqueira
>>
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to django-users...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/CACX1ULQ4kMb%2BfdrkfZg0KvBUyfha6zbNDU1u1Grg9cFP_gfR9g%40mail.gmail.com
>>  
>> 
>> .
>>
>
>
> -- 
> Fábio C. Barrionuevo da Luz
> Palmas - Tocantins - Brasil - América do Sul
>
> http://pythonclub.com.br/
>
> Blog colaborativo sobre Python e tecnologias Relacionadas, mantido 
> totalmente no https://github.com/pythonclub/pythonclub.github.io .
>
> Todos são livres para publicar. É só fazer fork, escrever sua postagem e 
> mandar o pull-request. Leia mais sobre como publicar em README.md e 
> contributing.md.
> Regra básica de postagem:
> "Você" acha interessante? É útil para "você"? Pode ser utilizado com 
> Python ou é útil para quem usa Python? Está esperando o que? Publica logo, 
> que estou louco para ler...
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/0cf132a5-79b6-45d9-84d5-d3bc2982cce9n%40googlegroups.com.

Re: how to convert to Django 3 or 4

['Steven Mapes' via Django users]

I've used it to go from Django 3 to 4 and to move a project from 1.11 to
2.2.

It doesn't do everything for you but it's a great start. I've personally
moved from 1.8 through to 4.2.2 but that was during their development
lifecycle. Moving up to 1.7 and then 1.7 to 1.8 and 1.8 to 1.11 and 1.11 to
2 will be the hardest parts but it'll get easier once you're on 1.11

On Thu, Jun 8, 2023, 19:58 Rogério Carrasqueira <
rogerio.carrasque...@gmail.com> wrote:

> Hey Steven!
>
> Thanks for this information, do you have tried it before? I would like to
> move from 1.4 to lastest, do you think that is it possible?
>
> Thanks
>
> Em quarta-feira, 7 de junho de 2023 às 11:52:35 UTC-3, Steven Mapes
> escreveu:
>
>> I'd suggest looking into using Adam Johnson's Django-Upgrade told -
>> https://github.com/adamchainz/django-upgrade it will help you move
>> between versions
>>
>> On Tuesday, 6 June 2023 at 15:24:36 UTC+1 Paul Haguet wrote:
>>
>>> There is a lot of function who can change.
>>>
>>> https://docs.djangoproject.com/en/4.2/releases/4.0/
>>>
>>> All the function declared as deprecated into Django 3 has been removed
>>> into Django 4. In the deprecated section of django 3 new functions names
>>> are systematically indicated. So just search the function under their old
>>> name and replace them with their new name. The 2 links below give the list.
>>>
>>>
>>> https://docs.djangoproject.com/en/4.2/releases/3.0/#deprecated-features-3-0
>>>
>>> https://docs.djangoproject.com/en/4.2/releases/3.1/#deprecated-features-3-1
>>>
>>> Le samedi 3 juin 2023 à 10:10:31 UTC+2, Shams Ulhaq a écrit :
>>>
 Just need to change url import

 from django.urls import include, re_path as url


 On Sat, 3 Jun 2023, 12:32 David Nugent,  wrote:

> nppe url is obsolete and removed in 4.x.
>
> You can use re_path, which is a kind of replacement but even then you
> will need to adjust the regex in many cases.
>
> The best approach is to understand what the url() is doing, and
> replicate the same using path(). Once you do, the conversions should be
> more or less straight-forward. Instead of regex you use labelled patterns
> making for more comprehensible path lines. For complex regex expressions
> you may need to define custom matches - or "converters" - that enforce
> specific patterns allowing you to restrict input and improve matching. 
> This
> is one area that Django has improved really well over time.
>
> But, like I said, don't try to replace this file wholesale. Instead of
> converting it and doing error-fix-error-fix ad infinitun, re-implement
> things as you enable parts of the app you have successfully ported. While
> re_path may be a fallback, try to re-implement as path() expressions and
> you'll be better in the long run.
>
>
> On Sat, Jun 3, 2023 at 11:59 AM Muhammad Juwaini Abdul Rahman <
> juw...@gmail.com> wrote:
>
>> I think Django 4 still have backward compatibility with `url`
>> although `path` is preferable.
>>
>> You can try to `runserver` in your local, upgrade your django version
>> in your virtualenv to version 4 and troubleshoot the error messages (if
>> any) one by one.
>>
>> On Sat, 3 Jun 2023 at 05:20, john fabiani 
>> wrote:
>>
>>> Hi everyone,
>>>
>>> I am tasked with updating/upgrading a very old Django web site - I
>>> believe it is 1.7.  I need convert and need what is required.
>>> Thanks in advance.
>>>
>>>
>>> I need to convert the following:
>>>
>>> from django.conf.urls import patterns, include, url
>>> from django.contrib import admin
>>> from django.conf import settings
>>> from django.conf.urls.static import static
>>>
>>> urlpatterns = patterns('',
>>> # Examples:
>>> url(r'reg4/$', 'register.views.reg4', name='reg4'),
>>> url(r'reg3/$', 'register.views.reg3', name='reg3'),
>>> url(r'reg2/$', 'register.views.reg2', name='reg2'),
>>> #url(r'reg1/$', 'register.views.reg1', name='reg1'),
>>> url(r'reg1/$', 'register.views.reg1', name='reg1'),
>>> #url(r'^$', 'register.views.home', name='home'),
>>> url(r'reg/$', 'register.views.home', name='home'),
>>> url(r'get_courts/(\d+)$', 'register.views.get_courts',
>>> name='get_courts'),
>>> url(r'get_courses/(\d+)$', 'register.views.get_courses',
>>> name='get_courses'),
>>> url(r'autoschedule/', 'register.views.autoschedule',
>>> name='autoschedule'),
>>> url(r'get_cities/(\d+)$', 'register.views.get_cities',
>>> name='get_cities'),
>>> url(r'get_classes/(\d+)$', 'register.views.get_classes',
>>> name='get_classes'),
>>> url(r'get_cities2/(\d+)/(\d+)/$', 'register.views.get_cities2',
>>> name='get_cities2'),
>>> url(r'get_classes2/(\d+)/(\d+)/$',
>>> 'register.views.get_classes2', name='get_cl

Re: CSV file

[Muhammad Juwaini Abdul Rahman]

How big is the file?

I don't think a mere 2K records can kill an 8GB RAM machine.

Probably something to do with your workers' settings?

On Fri, 9 Jun 2023 at 03:02, Percy Masekwameng <
percymasekwameng...@gmail.com> wrote:

> Hi
>
> I have web app survey that collect data and generate a CSV file,
> I'm using railway to deploy my web app, running on 8GB RAM and each time I
> generate a file, the server goes down and display "Application failed to
> respond" the database table has over 2k records
> Is there any way to improve the performance so that I can be able to
> download large dataset from the web app?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CANfc-pBoutR0kD%3DcqwRHGSQ8gac%2B_YLMyCQoFK--%3DD54TZpotA%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAFKhtoTkSsNMcvOZgP%2BWw2U2%3DMkfpD4%3DFLiNUL-Ftd1xzAi4uA%40mail.gmail.com.

Re: how to convert to Django 3 or 4

[אורי]

Hi,

I think you can try to upgrade LTS to LTS. That is, upgrade to the next
LTS, then the next LTS, and not directly to Django 4.2. With each LTS check
that the site is working. And also, I would recommend using the latest
Django release only 6 months after the initial release, because all your
dependencies have to upgrade and also bug fixes. So use Django 4.1 now, and
Django 4.2 only on October 2023.

If you have a problem with something not working, read the release notes of
the specific versions and search for the function not working. For example,
search for "url" on the page (control-f in the browser).

Good luck!

Uri Rodberg, Speedy Net.
אורי
u...@speedy.net


On Fri, Jun 2, 2023 at 11:20 PM john fabiani  wrote:

> Hi everyone,
>
> I am tasked with updating/upgrading a very old Django web site - I believe
> it is 1.7.  I need convert and need what is required.
> Thanks in advance.
>
>
> I need to convert the following:
>
> from django.conf.urls import patterns, include, url
> from django.contrib import admin
> from django.conf import settings
> from django.conf.urls.static import static
>
> urlpatterns = patterns('',
> # Examples:
> url(r'reg4/$', 'register.views.reg4', name='reg4'),
> url(r'reg3/$', 'register.views.reg3', name='reg3'),
> url(r'reg2/$', 'register.views.reg2', name='reg2'),
> #url(r'reg1/$', 'register.views.reg1', name='reg1'),
> url(r'reg1/$', 'register.views.reg1', name='reg1'),
> #url(r'^$', 'register.views.home', name='home'),
> url(r'reg/$', 'register.views.home', name='home'),
> url(r'get_courts/(\d+)$', 'register.views.get_courts',
> name='get_courts'),
> url(r'get_courses/(\d+)$', 'register.views.get_courses',
> name='get_courses'),
> url(r'autoschedule/', 'register.views.autoschedule',
> name='autoschedule'),
> url(r'get_cities/(\d+)$', 'register.views.get_cities',
> name='get_cities'),
> url(r'get_classes/(\d+)$', 'register.views.get_classes',
> name='get_classes'),
> url(r'get_cities2/(\d+)/(\d+)/$', 'register.views.get_cities2',
> name='get_cities2'),
> url(r'get_classes2/(\d+)/(\d+)/$', 'register.views.get_classes2',
> name='get_classes2'),
> url(r'rejected/$', 'register.views.rejected', name='rejected'),
> url(r'finished/$', 'register.views.finished', name='finished'),
>
> ##url(r'^$', 'profiles.views.home', name='home'),
> #url(r'^contact/$', 'register.views.home', name='contact'),
> #url(r'^about/$', 'register.views.about', name='about'),
> #url(r'^profile/$', 'register.views.user_profile', name='profile'),
> #url(r'^checkout/$', 'checkout.views.checkout', name='checkout'),
> # url(r'^blog/', include('blog.urls')),
>
> url(r'^admin/', include(admin.site.urls)),
> ) + static(settings.STATIC_URL, document_root = settings.STATIC_ROOT)
>
> What is required?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/8f8a68b4-a3c5-a10d-8246-2ef41635b406%40jfcomputer.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CABD5YeFHT4CCtbqbT06eX815WKvH%3DH%3DO9tYGdOCeyRm438iaoA%40mail.gmail.com.

Re: CSV file

[Percy Masekwameng]

It depends on the data in the database

Explain more about workers settings and provide me with an example

On Fri, 9 Jun 2023, 02:24 Muhammad Juwaini Abdul Rahman, 
wrote:

> How big is the file?
>
> I don't think a mere 2K records can kill an 8GB RAM machine.
>
> Probably something to do with your workers' settings?
>
> On Fri, 9 Jun 2023 at 03:02, Percy Masekwameng <
> percymasekwameng...@gmail.com> wrote:
>
>> Hi
>>
>> I have web app survey that collect data and generate a CSV file,
>> I'm using railway to deploy my web app, running on 8GB RAM and each time
>> I generate a file, the server goes down and display "Application failed to
>> respond" the database table has over 2k records
>> Is there any way to improve the performance so that I can be able to
>> download large dataset from the web app?
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to django-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-users/CANfc-pBoutR0kD%3DcqwRHGSQ8gac%2B_YLMyCQoFK--%3DD54TZpotA%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CAFKhtoTkSsNMcvOZgP%2BWw2U2%3DMkfpD4%3DFLiNUL-Ftd1xzAi4uA%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CANfc-pBv8u_sGNP%3DZhJL6sG3RHvXRuHXn0M17_vvPa8f2UYkjQ%40mail.gmail.com.

Re: CSV file

[Prosper Lekia]

Ask this question on the Railway Discord community. The expert their will
tell you if it's a Railway thing or not. But you should look more at your
code, your settings.py.

On Thu, Jun 8, 2023, 20:03 Percy Masekwameng 
wrote:

> Hi
>
> I have web app survey that collect data and generate a CSV file,
> I'm using railway to deploy my web app, running on 8GB RAM and each time I
> generate a file, the server goes down and display "Application failed to
> respond" the database table has over 2k records
> Is there any way to improve the performance so that I can be able to
> download large dataset from the web app?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CANfc-pBoutR0kD%3DcqwRHGSQ8gac%2B_YLMyCQoFK--%3DD54TZpotA%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CALGeGE23%2BpbHmf-UC0M04cMnQr-Dg%3DMcoPsOZvDzBXPBOL-jFA%40mail.gmail.com.

Re: CSV file

[Muhammad Juwaini Abdul Rahman]

Probably you need to show the code snippet on where you generate the csv
file.

On Fri, 9 Jun 2023 at 13:51, Percy Masekwameng <
percymasekwameng...@gmail.com> wrote:

> It depends on the data in the database
>
> Explain more about workers settings and provide me with an example
>
> On Fri, 9 Jun 2023, 02:24 Muhammad Juwaini Abdul Rahman, <
> juwa...@gmail.com> wrote:
>
>> How big is the file?
>>
>> I don't think a mere 2K records can kill an 8GB RAM machine.
>>
>> Probably something to do with your workers' settings?
>>
>> On Fri, 9 Jun 2023 at 03:02, Percy Masekwameng <
>> percymasekwameng...@gmail.com> wrote:
>>
>>> Hi
>>>
>>> I have web app survey that collect data and generate a CSV file,
>>> I'm using railway to deploy my web app, running on 8GB RAM and each time
>>> I generate a file, the server goes down and display "Application failed to
>>> respond" the database table has over 2k records
>>> Is there any way to improve the performance so that I can be able to
>>> download large dataset from the web app?
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Django users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to django-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/django-users/CANfc-pBoutR0kD%3DcqwRHGSQ8gac%2B_YLMyCQoFK--%3DD54TZpotA%40mail.gmail.com
>>> 
>>> .
>>
>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to django-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-users/CAFKhtoTkSsNMcvOZgP%2BWw2U2%3DMkfpD4%3DFLiNUL-Ftd1xzAi4uA%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CANfc-pBv8u_sGNP%3DZhJL6sG3RHvXRuHXn0M17_vvPa8f2UYkjQ%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAFKhtoQypbdPf9k1w9LM1wgZWSOqbs7d8XwRqdVm%3D3xm-kYtEQ%40mail.gmail.com.

Re: how to convert to Django 3 or 4

['Steven Mapes' via Django users]

If you want to go directly then start a new project and "lift and shift"
code fixing and updating as you go. Depending on the size of the project
and the complexity of the processes it may be the fastest way to do it.

If you want to keep the same project then upgrade in stages. The fact
you're in 1.4 will make it hard and you'll need to do a lot of manual
changes to get into 1.8 so starting new may well be quicker. If you did
upgrade then I'd go 1.8 to 1.11, 2.2, 3.2 and finally 4.2.

Branch the code using version control and see how bad it is but it'll
depend on the project.
I went from 1.11 to 3.2 in a day for one but most of the code was bespoke
without may external packages to worry about. Those could also cause you
issues.

Since the code is Django 1.4 what version of python is it also using?


On Thu, Jun 8, 2023, 21:31 Rogerio Carrasqueira <
rogerio.carrasque...@gmail.com> wrote:

> So just to undersand, I cannot move directly from 1.4 to 4 I have to do it
> in steps, right?
>
> Thanks
> Rogério Carrasqueira
>
>
>
>
>
> Em qui., 8 de jun. de 2023 às 17:01, 'Steven Mapes' via Django users <
> django-users@googlegroups.com> escreveu:
>
>> I've used it to go from Django 3 to 4 and to move a project from 1.11 to
>> 2.2.
>>
>> It doesn't do everything for you but it's a great start. I've personally
>> moved from 1.8 through to 4.2.2 but that was during their development
>> lifecycle. Moving up to 1.7 and then 1.7 to 1.8 and 1.8 to 1.11 and 1.11 to
>> 2 will be the hardest parts but it'll get easier once you're on 1.11
>>
>> On Thu, Jun 8, 2023, 19:58 Rogério Carrasqueira <
>> rogerio.carrasque...@gmail.com> wrote:
>>
>>> Hey Steven!
>>>
>>> Thanks for this information, do you have tried it before? I would like
>>> to move from 1.4 to lastest, do you think that is it possible?
>>>
>>> Thanks
>>>
>>> Em quarta-feira, 7 de junho de 2023 às 11:52:35 UTC-3, Steven Mapes
>>> escreveu:
>>>
 I'd suggest looking into using Adam Johnson's Django-Upgrade told -
 https://github.com/adamchainz/django-upgrade it will help you move
 between versions

 On Tuesday, 6 June 2023 at 15:24:36 UTC+1 Paul Haguet wrote:

> There is a lot of function who can change.
>
> https://docs.djangoproject.com/en/4.2/releases/4.0/
>
> All the function declared as deprecated into Django 3 has been removed
> into Django 4. In the deprecated section of django 3 new functions names
> are systematically indicated. So just search the function under their old
> name and replace them with their new name. The 2 links below give the 
> list.
>
>
> https://docs.djangoproject.com/en/4.2/releases/3.0/#deprecated-features-3-0
>
> https://docs.djangoproject.com/en/4.2/releases/3.1/#deprecated-features-3-1
>
> Le samedi 3 juin 2023 à 10:10:31 UTC+2, Shams Ulhaq a écrit :
>
>> Just need to change url import
>>
>> from django.urls import include, re_path as url
>>
>>
>> On Sat, 3 Jun 2023, 12:32 David Nugent,  wrote:
>>
>>> nppe url is obsolete and removed in 4.x.
>>>
>>> You can use re_path, which is a kind of replacement but even then
>>> you will need to adjust the regex in many cases.
>>>
>>> The best approach is to understand what the url() is doing, and
>>> replicate the same using path(). Once you do, the conversions should be
>>> more or less straight-forward. Instead of regex you use labelled 
>>> patterns
>>> making for more comprehensible path lines. For complex regex expressions
>>> you may need to define custom matches - or "converters" - that enforce
>>> specific patterns allowing you to restrict input and improve matching. 
>>> This
>>> is one area that Django has improved really well over time.
>>>
>>> But, like I said, don't try to replace this file wholesale. Instead
>>> of converting it and doing error-fix-error-fix ad infinitun, 
>>> re-implement
>>> things as you enable parts of the app you have successfully ported. 
>>> While
>>> re_path may be a fallback, try to re-implement as path() expressions and
>>> you'll be better in the long run.
>>>
>>>
>>> On Sat, Jun 3, 2023 at 11:59 AM Muhammad Juwaini Abdul Rahman <
>>> juw...@gmail.com> wrote:
>>>
 I think Django 4 still have backward compatibility with `url`
 although `path` is preferable.

 You can try to `runserver` in your local, upgrade your django
 version in your virtualenv to version 4 and troubleshoot the error 
 messages
 (if any) one by one.

 On Sat, 3 Jun 2023 at 05:20, john fabiani 
 wrote:

> Hi everyone,
>
> I am tasked with updating/upgrading a very old Django web site - I
> believe it is 1.7.  I need convert and need what is required.
> Thanks in advance.
>
>
> I need to convert the following:
>

Re: CSV file

[Peter Benjamin Ani]

Try using Python anywhere

On Fri, 9 Jun 2023 at 07:15, Muhammad Juwaini Abdul Rahman <
juwa...@gmail.com> wrote:

> Probably you need to show the code snippet on where you generate the csv
> file.
>
> On Fri, 9 Jun 2023 at 13:51, Percy Masekwameng <
> percymasekwameng...@gmail.com> wrote:
>
>> It depends on the data in the database
>>
>> Explain more about workers settings and provide me with an example
>>
>> On Fri, 9 Jun 2023, 02:24 Muhammad Juwaini Abdul Rahman, <
>> juwa...@gmail.com> wrote:
>>
>>> How big is the file?
>>>
>>> I don't think a mere 2K records can kill an 8GB RAM machine.
>>>
>>> Probably something to do with your workers' settings?
>>>
>>> On Fri, 9 Jun 2023 at 03:02, Percy Masekwameng <
>>> percymasekwameng...@gmail.com> wrote:
>>>
 Hi

 I have web app survey that collect data and generate a CSV file,
 I'm using railway to deploy my web app, running on 8GB RAM and each
 time I generate a file, the server goes down and display "Application
 failed to respond" the database table has over 2k records
 Is there any way to improve the performance so that I can be able to
 download large dataset from the web app?

 --
 You received this message because you are subscribed to the Google
 Groups "Django users" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to django-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/django-users/CANfc-pBoutR0kD%3DcqwRHGSQ8gac%2B_YLMyCQoFK--%3DD54TZpotA%40mail.gmail.com
 
 .
>>>
>>>
 --
>>> You received this message because you are subscribed to the Google
>>> Groups "Django users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to django-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/django-users/CAFKhtoTkSsNMcvOZgP%2BWw2U2%3DMkfpD4%3DFLiNUL-Ftd1xzAi4uA%40mail.gmail.com
>>> 
>>> .
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to django-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-users/CANfc-pBv8u_sGNP%3DZhJL6sG3RHvXRuHXn0M17_vvPa8f2UYkjQ%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CAFKhtoQypbdPf9k1w9LM1wgZWSOqbs7d8XwRqdVm%3D3xm-kYtEQ%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAPxt_2VmNUywXmtX__ZyVkOxsDO8P37Ef7UHRcx5wvXPgwqKrg%40mail.gmail.com.