I'm sorry. Thank you for information.
17 Temmuz 2019 Çarşamba 18:43:54 UTC+3 tarihinde Adam Johnson yazdı:
>
> Hi!
>
> I think you've found the wrong mailing list for this post. This mailing
> list is for the development of Django itself, not for support using Django.
> This means the discussion
Hi!
I think you've found the wrong mailing list for this post. This mailing
list is for the development of Django itself, not for support using Django.
This means the discussions of bugs and features in Django itself, rather
than in your code using it. People on this list are unlikely to answer yo
Hello dear friends, I will develop web app with Django. How should be
folder structure my project.
--
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 f
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" wrote:
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
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 o
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 itsel
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
l 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 everythin
>
>> 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 File wrapp
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.
>
> This happened with django 1.10 and I believe it wasn't changed with Django
> 1.11
>
> --
> You received this message beca
ngo'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 from the .io
module or simply the object returned by open() (python 2) supports the
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 sess
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 b
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
French
> 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 storage backends do where there is an
> > existin
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
wrote:
> You can create a Django file object from any file-like object just by
> passing it to the constructor.
>
> django.cor
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 to
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 with it ?
19 matches
Mail list logo
