Re: DJANGO FILE

2019-02-13 Thread Adam Johnson
The django documentation can be downloaded as PDF by following the link on the right of its index page: https://docs.djangoproject.com/en/2.1/ On Wed, 13 Feb 2019 at 08:48, Edward Victorhez wrote: > Good evening, please can I get the PDF note? > > On Feb 12, 2019 10:17 AM, "Adam Johnson"

Re: DJANGO FILE

2019-02-13 Thread Edward Victorhez
Good evening, please can I get the PDF note? On Feb 12, 2019 10:17 AM, "Adam Johnson" wrote: > Hi Edward, > > You probably want the Django "start" page: https://www. > djangoproject.com/start/ > > Emailing this mailing list of more than 10,000 addresses for such help is > not appropriate. It is

Re: DJANGO FILE

2019-02-12 Thread Adam Johnson
Hi Edward, You probably want the Django "start" page: https://www.djangoproject.com/start/ Emailing this mailing list of more than 10,000 addresses for such help is not appropriate. It is for discussion of the creation of Django itself. For other places to go see the "Join the community" header

Re: DJANGO FILE

2019-02-11 Thread Kosta Dafoulas
I’ll give you the files On Mon, Feb 11, 2019 at 10:18 AM Edward Victorhez wrote: > PLEASE I AM NEW IN DJANGO, PLEASE I NEED THE FILES THAT WILL PUT ME > THROUGH > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django

DJANGO FILE

2019-02-11 Thread Edward Victorhez
PLEASE I AM NEW IN DJANGO, PLEASE I NEED THE FILES THAT WILL PUT ME THROUGH -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email

Re: Should django File wrapper support .next()?

2017-08-18 Thread Adam Johnson
ext() call would start to fail, since although django's File is >>> iterable, it doesn't define the next method. >>> >>> Now I'm wondering if this is on purpose, or a bug. It's odd that every >>> stream (or almost) from the python library such as everything fro

Re: Should django File wrapper support .next()?

2017-08-16 Thread Cristiano Coelho
I'm wondering if this is on purpose, or a bug. It's odd that every >> stream (or almost) from the python library such as everything from the .io >> module or simply the object returned by open() (python 2) supports the next >> call but the django File wrapper doesn't. >&

Re: Should django File wrapper support .next()?

2017-08-15 Thread Adam Johnson
hing from the .io > module or simply the object returned by open() (python 2) supports the next > call but the django File wrapper doesn't. > > This happened with django 1.10 and I believe it wasn't changed with Django > 1.11 > > -- > You received this message because you are subscri

Should django File wrapper support .next()?

2017-07-27 Thread Cristiano Coelho
File is iterable, it doesn't define the next method. Now I'm wondering if this is on purpose, or a bug. It's odd that every stream (or almost) from the python library such as everything from the .io module or simply the object returned by open() (python 2) supports the next call but the django

Re: Django File-based session doesn't expire

2012-04-19 Thread Paul McMillan
Hi, This is explained in the docs about sessions: https://docs.djangoproject.com/en/dev/topics/http/sessions/#clearing-the-session-table We provide a job you can periodically run to remove expired sessions. However, looking at the code, it appears that this only works for the database backed

Re: Django File-based session doesn't expire

2012-04-19 Thread ej
Anyone? On Tuesday, April 17, 2012 4:11:28 PM UTC-7, ej wrote: > > File-based session backend doesn't expire, unlike db-backed and > cache-based sessions. I'm not too sure if this is a bug or an intended (but > undocumented) design. I am under the impression that all session backends > should

Django File-based session doesn't expire

2012-04-17 Thread ej
File-based session backend doesn't expire, unlike db-backed and cache-based sessions. I'm not too sure if this is a bug or an intended (but undocumented) design. I am under the impression that all session backends should behave similarly. If this is an intended design, can someone explains why

Re: make the File Storage API works with a file-like object instead of the Django File object.

2012-02-29 Thread Michael
, Feb 28, 2012 at 3:29 PM, Jonathan French <m...@jonathanfrench.net> > wrote: > > You can create a Django file object from any file-like object just by > > passing it to the constructor. > > > django.core.files.File(my_file_like_object) > > > This is basically what all the

Re: make the File Storage API works with a file-like object instead of the Django File object.

2012-02-28 Thread Paul McMillan
This ticket is related to the issue: https://code.djangoproject.com/ticket/16946 -Paul On Tue, Feb 28, 2012 at 3:29 PM, Jonathan French <m...@jonathanfrench.net> wrote: > You can create a Django file object from any file-like object just by > passing it to the

Re: make the File Storage API works with a file-like object instead of the Django File object.

2012-02-28 Thread Jonathan French
You can create a Django file object from any file-like object just by passing it to the constructor. django.core.files.File(my_file_like_object) This is basically what all the storage backends do where there is an existing file object from whatever source, and what you have to do if you want

make the File Storage API works with a file-like object instead of the Django File object.

2012-02-28 Thread Michael
Hi, The File Storage API only works with the Django File object (https:// docs.djangoproject.com/en/1.3/ref/files/storage/ ; https://docs.djangoproject.com/en/1.3/ref/files/file/). Wouldn't it be a good idea to make a Django file-like object instead and make the Storage API works