It still seems to have a bug when just doing .select_related(depth=1),
sometimes its filling the field w/ the wrong data, looking into it.
On Jan 11, 11:31 am, "David Cramer" <[EMAIL PROTECTED]> wrote:
> I retract my statement, we had some other random server configuratio
On 1/12/07, Andrew Durdin <[EMAIL PROTECTED]> wrote:
> Can you explain the reasons why one would want to use signed cookies?
> What (presumably security) issues are they intended to overcome?
Stateless server. Rather than provide a randomized session token to
the user and associate that token wit
and will
probably draw in a lot of people -- I think it'd be beneficial to
make sure all the documentation is in place before the big rush :)
---
David Zhou
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed
l possibilities so let's get back to the
discussion.
Cheers,
David
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@goo
d you have your main django site running at
domain.com, using FCGI for both will dramatically reduce memory
requirements.
You don't really want to be embedding both a PHP and a Python
interpreter in each non-media Apache call.
---
David Zhou
[EMAIL PROTECTED]
--~--~-~--~---
ases
> > and security issues, right? You should send a message to that list
> > announcing the patch.
>
> I will once I've backported it. The question in my mind is just
> whether we need 0.95.2 from this.
I'm +1 on this option. Before making decision what about at lea
2007/1/30, Russell Keith-Magee <[EMAIL PROTECTED]>:
>
> On 1/30/07, David Larlet <[EMAIL PROTECTED]> wrote:
> > I'm +1 on this option. Before making decision what about at least add
> > a warning message on the documentation page?
>
> This is kind of the
ase, they can be used by end users on their own forms.
>
I totally agree with this interesting proposition. Forms are not that
hard to htmlize but always take time, with those classes it could be
incredibly fast.
Cheers,
David
--~--~-~--~~~---~--~~
You received
n for
long term stats.
What about an optional stats view in the admin interface?
Cheers,
David
[1] : http://bbclone.de
[2] : http://bbclone.de/demo/show_detailed.php
[3] : http://www.throwingbeans.org/peastat.html
--~--~-~--~~~---~--~~
You received this message
what do you think?
We had to consider both options:
* live stats which tail apache log to track current visitors
* long term stats which store number of access/page, incoming keywords, etc
Maybe the second part can be done by AW stats or third party tool as
John suggests.
David
--~--~---
's a good thing
to let django doing this job because other tools already did this
really well, maybe just having a view from one of those tools in the
admin view could be the best compromise (as zenx suggests).
Anyway, thanks for all your suggestions and interesting links (thanks
Grah
blog) with customized
middleware, templatetags, generic views is missing. Reading a doc is
boring, following a tutorial, even if it's a big one, which reflect a
real application with real problems is always appreciated.
I've already linked the symfony askeet project [1] which is a goo
quot; doc but,
except if you decide to transfer all your posts, it's an essential
resource, so... I hope you have redundancy on your server ;-).
David
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django d
What's wrong with this picture?
TimeDivision.objects.filter(when__ge=datetime(2007,5,14))
Whoops. "Greater or equal" is spelled 'gte' and not 'ge' in Django's
model API. After having fallen into this trap and getting a cryptic
error message (UnboundLocalError: local variable 'new_opts' refer
David Abrahams
<[EMAIL PROTECTED]> writes:
> ---
> from django.models import field as _
>
> Entry.objects.filter(
> _.headline.startswith('What')).exclude(
> _.pub_date>=datetime.now()).filter(
> _.pub_date>=datetime(200
"Russell Keith-Magee"
<[EMAIL PROTECTED]> writes:
> On 2/10/07, David Abrahams <[EMAIL PROTECTED]> wrote:
>>
>>Use natural operators for filtering, excluding, and attribute
>>access.
>
>> How about it?
>
> Some immediate proble
Malcolm Tredinnick <[EMAIL PROTECTED]>
writes:
> On Sat, 2007-02-10 at 08:30 +0800, Russell Keith-Magee wrote:
>> On 2/10/07, David Abrahams <[EMAIL PROTECTED]> wrote:
>> >
>> >Use natural operators for filtering, excluding, and attribute
>> &g
"Lawrence Oluyede" <[EMAIL PROTECTED]>
writes:
>> > ---
>> > from django.models import field as _
>> >
>> > Entry.objects.filter(
>> > _.headline.startswith('What')).exclude(
>> > _.pub_date>=datetime.now()).filter(
>> > _.pub_date>=datetime(2005, 1, 1))
>>
>> Should b
Malcolm Tredinnick <[EMAIL PROTECTED]>
writes:
> On Fri, 2007-02-09 at 21:14 -0500, David Abrahams wrote:
>> _.foo >= 6 returns an expression tree, an object that represents
>> the comparison of the foo field with 6. This technique is well-known
>> among advance
ntation *considerably* more arcane.
I *seriously* doubt that. This feature is really simple to implement.
Maybe I'll have to code it to prove that, but from the number of "I'm
not a fan of..." responses I'm seeing here, I doubt that knowing it's
simple would make much d
"Karen Tracey" <[EMAIL PROTECTED]>
writes:
> On 2/9/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
> However, you have obviously been bitten by a bad error message - I
> would suggest that a good course of action would be to raise a ticket
> with your specific example so that th
"Adrian Holovaty" <[EMAIL PROTECTED]>
writes:
> On 2/9/07, David Abrahams <[EMAIL PROTECTED]> wrote:
>> Entry.objects.filter(
>> _.headline.startswith('What') &
>> ~(_.pub_date>=datetime.now()) &
>>
"Karen Tracey" <[EMAIL PROTECTED]>
writes:
> "Karen Tracey" <[EMAIL PROTECTED]>
> writes:
> > The fix for #2348 changes the error from "Unbound local error" to "Type
> error: cannot
> resolve
> > keyword [whatever] into field".
>
> Illustrating just why the current sy
min) is not as usable as it could be. And even better, it would
simplify managing the auth-system as a whole (only small apps, that
implement, provide or use some API).
Greetings, David Danier
P.S.: Sorry about the missing "In-Reply-To"-Header, I just joined this list.
--~--~-
ormal Django-way
(Admin-subclass...).
But it's nice to see separation the admin from the auth-app is on its
way already.
Greetings, David Danier
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django deve
t care about that ?
Have a look at this bug: http://code.djangoproject.com/ticket/3268 It
still need tests.
Hope that helps,
David
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
T
easy. But I think allowing the user to explicit use UPDATE or
INSERT would be a nice feature.
Greetings, David Danier
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to th
7;s a good start for a part of the
world.
Cheers,
David Larlet
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To
ependent of
save() and can be called directly (if you know what you do). Anyhow
there needs to be some logic inside save(), of course.
I'm not familiar with the current implementation of save(), so I don't
know how complex it would be to accomplish this, but it sounds easy
ackends-system obsolete (sorry), but keeps
its flexibility while making things simpler for application-developers.
For the permissions-system I would do similar.
(One configuration-directive, some API thats fixed but allows model- and
row-level-permissions)
If you are interested I could try to contri
t annoying because I
got an UnicodeError which drive me crazy before I verify the argument
order.
I know it's easy to type label= for all newforms fields but maybe we
can reorder arguments in newforms before 0.96? What's your opinion
about that? Am
follow your coding-style here, but I'm willing to change
that if I get some positive response on this.
Greetings, David Danier
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers&qu
is not always at the same argument place, I
doubt that it breaks previous code because you "need" to specify
label=
David
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group
> I found this query that isn't quoted correctly (I trimmed out some
> stuff to make this shorter):
AFAIK the queries are logged without quoting but executed correctly.
(You can see this, if you have a SQL-error and the DB-backends throws an
exception with the real query)
Greet
I've uploaded a new patch against the oracle branch and updated the
backend module.
You can check http://code.djangoproject.com/ticket/1261
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
s there a real advantage over using this?
(except for looking nicer)
8<-
from django.db.models.loading import get_model
[...]
models.ForeignKey(get_model('account', 'User'))
->8
Greetings, David Danier
--
nt. But I haven't seen this so far, nor searched for
it. ;-)
Greetings, David Danier
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to dj
any interface.
Greetings, David Danier
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from thi
2007/3/6, David Larlet <[EMAIL PROTECTED]>:
> Hi,
>
> I got some troubles today with newforms. I use to create models fields
> with a first implicit verbose_name argument:
> email = models.EmailField("E-mail")
>
> Unfortunately newforms fields have quite si
_ than a binary
representation."
Besides the other methods provide some optimization:
"Protocol version 2 was introduced in Python 2.3. It provides much _more
efficient_ pickling of new-style classes."
Just my 2 cents,
David Danier
--~--~-~--~~~--
nk this should stay default.
Greetings, David Danier
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsub
st_comment', name="%(load_func)s.post_comment"),
)
---->8---
Perhaps this case is to specific to be added to a {% url %} refactoring,
but if it can be done on the way it should be considered. Would really
improve what you
this model for professional use, may I know if this part
of the admin is stable and is not intended to be removed in the new
branch?
Next question is how did you make the difference with signals
(post_save) between creation and modification of an item?
Thank
2007/4/3, Adrian Holovaty <[EMAIL PROTECTED]>:
>
> On 4/3/07, David Larlet <[EMAIL PROTECTED]> wrote:
> > I'd like to add a log for some objects of my project and after playing
> > a bit with signals, I remember that there is a similar "feature" in
&
o_now_add is fine, but writing
> a save() for every model that needs auto_now is just annoying. A
> shortcut would be nice.
I agree with Brian.
Regards,
David
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
well (for initial data). Currently I had to replace LazyDate with
datetime.now(), which is not lazy anymore (datetime.now as used for
models would be lazy). Perhaps this can be changed, too?
Greetings, David Danier
--~--~-~--~~~---~--~~
You received this message be
> Just use datetime.now without the function call parentheses.
Know this, doesn't work for newforms (initial value).
I added a ticket (including a patch) to fix this:
http://code.djangoproject.com/ticket/4018
David
--~--~-~--~~~---~--~~
You recei
rms don't need to do so)?
Greetings, David Danier
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscr
the patches:
http://dpaste.com/hold/9043/
svk patch help:
http://dpaste.com/hold/9044/
svk Homepage:
http://svk.bestpractical.com/
Greetings, David Danier
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
&quo
ve
RESTful implementation one day :-). I have added your contribution to
the feature grouping page:
http://code.djangoproject.com/wiki/FeatureGrouping#WebservicesREST
Regards,
David
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
efactoring it will
be possible.
__istartswith could be possible using STARTING, it uses index for
VARCHARS and works with BLOBS.
__iendswith is not possible (i could be wrong).
What you, django devs, think? If this backend would be added to trunk
should firebird 2.1 be the
ield's will be impossible,
maybe with some UDF.
IMO if it will be in trunk it should when firebird 2.1 is released.
David Elias
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers"
Russell Keith-Magee escreveu:
> On 3/17/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I'm afraid I don't see the benefit of what you are proposing. The
> serialization framework exists for the easy serialization of Django
> DB-backed objects - not for the arbitrary serialization of _any_
> ob
Regarding deserialization, i guess if a queryset will set these extra
columns to a model why not restore them?
David Elias
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post
Hi,
I'm just curious about SoC, especially the REST one, listed on this
page: http://code.google.com/soc/django/about.html
Maybe it's time to make an "official" announcement?
Regards,
David
--~--~-~--~~~---~--~~
You received this mes
2007/4/28, James Bennett <[EMAIL PROTECTED]>:
>
> On 4/28/07, David Larlet <[EMAIL PROTECTED]> wrote:
> > I'm just curious about SoC, especially the REST one, listed on this
> > page: http://code.google.com/soc/django/about.html
> >
> > Maybe it'
2007/4/29, Jay Parlar <[EMAIL PROTECTED]>:
>
> On 4/28/07, David Larlet <[EMAIL PROTECTED]> wrote:
> > I just hope those ones will be successful! Maybe we can learn from the
> > past and improve students/dev communication in order to help them a
> > bit more
y default, instead this can go into a different application).
But the code seems mature and working, only some details are missing, if
the current auth-solution should be kept.
(Changing this might be better for post-1.0...but adding this now and
changing it later may be worse than changing it no
the last months on the feature grouping page:
http://code.djangoproject.com/wiki/FeatureGrouping#WebservicesREST
Hope it helps, I'm waiting for the example to comment your choices.
David
--~--~-~--~~~---~--~~
You received this message because you are sub
(_clean_FIELD/clean__FIELD)?
validate_FIELD sounds right, too.
Greetings, David Danier
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-devel
replaced by cleaned_data")
clean_data = property(_clean_data_error)
[...]
Classes extending this can override clean_data with some method
validating a data-field, users get some nice message, full_clean()
writes to cleaned_data and this can be removed in the realese after the
next one.
Greetin
On 07-May-14, at 5:47 AM, Russell Keith-Magee wrote:
> To my mind, editing relations in both directions on a form is no
> different to being able to query in both directions in a filter
> statement.
I agree. Being able to create forms from multiple models would be
killer. No application of us
;https://github.com/shangxiao/stupid-django-tricks/blob/master/all_subqueries/models.py#L119>
I found this work well for my codebase and I'd love to explore contributing
it back to Django. I'd suggest the subquery subclass as it results in more
readable code – but there is the question a
Filter: (abalance = 0)
Rows Removed by Filter: 8
Planning Time: 0.206 ms
Execution Time: 951.263 ms
(9 rows)
On Thursday, 25 August 2022 at 00:41:43 UTC+10 charettes wrote:
> Hello David,
>
> Do you know if ALL provides any performance benefits over NOT EXISTS?
> Give
about moving validation
to WHERE to get around issues with using SELECT but couldn't find any other
mention about how NULLs should be handled.
I wanted to check with folks here first before raising an issue. I'm not
sure what the fix should be but I'd recommend at least adding a
On Wed, 7 Sept 2022 at 15:37, אורי wrote:
>
> Hi David,
>
> Does and should Django connect directly to a remote SMTP server? Isn't it
> better to use the local mail server which will receive the email and then
> send it to a remote SMTP server? In my opinion, it&
Hi Pelumi,
It's kind of you to offer code, however there is a similar functionality in
contrib.humanize:
https://docs.djangoproject.com/en/4.1/ref/contrib/humanize/#naturaltime
Perhaps this does what you require?
--
David
On Fri, 9 Sept 2022 at 23:50, Bhuvnesh Sharma wrote:
> Hi,
was wondering what the rationale for that was? Would it be possible to
make the behaviour consistent? And if not - would a PR to clarify how
ValidationErrors are raised for constraints in the docs be welcomed?
Cheers,
David
--
You received this message because you are subscribed to the Google Groups
&quo
using the
error_messages dict… but I'll leave that for another post :)
Regards,
David
On Mon, 12 Sept 2022 at 11:53, charettes wrote:
> Hello David,
>
> This is expected because Django doesn't have a way to express the
> constraint in words to present to the user when a
...
AssertionError: {'__all__': ['Constraint “name_without_color_uniq” is
violated.']} != {'name': ['Constraint “name_without_color_uniq” is
violated.']}
- {'__all__': ['Constraint “name_without_color_uniq” is violated.']}
? ^^
+
ting the code based on the *constraint name*.
Single-field unique constraints already set the code "unique"; and this
works for field errors because there's usually only one unique constraint
defined for a field.
Thoughts?
Cheers,
David
--
You received this message because you ar
sql(compiler, connection)
+return "{}::{}".format(sql,
self.output_field.db_type(connection)), params
+
def __repr__(self):
return "{}({})".format(self.__class__.__name__, self.expression)
Any other ideas?
Regards,
David
--
You received thi
ep 24, 2022 at 5:51 PM Adam Taylor wrote:
>
>> Following the advice of David Sanders and Mariusz Felisiak, I'm coming
>> here with my proposal rather than continuing on with the ticket system (see
>> ticket
>> #34035 <https://code.djangoproject.com/ticket/3403
width and height as is read from the image with the
rotation as separate meta-data. (Eg I did a cursory look with Gimp &
Preview on mac)
On Mon, 26 Sept 2022 at 19:20, David Sanders
wrote:
> Coincidence I was also just reading up image-orientation… I didn't realise
> that it's t
/blob/0dd29209091280ccf34e07c9468746c396b7778e/django/core/files/images.py#L18-L24
Regards,
David
On Wed, 28 Sep 2022 at 07:13, 'Adam Johnson' via Django developers
(Contributions to Django itself) wrote:
> To have extra properties, we'd need to add extra database fields. It w
s? Use range types with
exclusion constraints.
- Only 1 column from a set of columns should be set? Use a check
constraint with an xor not null test.
- There are plenty more of these :)
Only the database can protect the data.
--
David
On Fri, 30 Sept 2022 at 10:12, Aaron Smith wrote:
>
ng performance
- A generator based solution would be nice if it could finish walking
early if used with any()
- Opinions on maintainability (readability) vs performance would be great
- Ideally I think it would be great if someone with some experience with
performant Python could c
>
> +1 for that, though this will need some careful design between perf
optimizations and how much general purpose it should be.
Perhaps before optimising we could start out with the basic readable
version and tailor it moving forward. It's possible this could be
irrelevant if it's only ever use
Hi,
I may be missing some context here but is this something distinctly
different from setting SQLite to use in-memory storage [1]? 🤔
[1] https://www.sqlite.org/inmemorydb.html
David
On Fri, 21 Oct 2022, 04:30 Paolo Melchiorre (paulox),
wrote:
> Hi all,
>
> there is a package tha
a documentation PR with some suggestions but
others may also doubt the value of adding a warning given that the very
next section explains how to do dynamic filtering. Personally I think by
the time you get to advanced Django such as this, Python experience is
assumed :)
Regards,
David
On Sun, 30
Hi Vasanth,
What advantages does a dropdown have over simply placing the options there
though? Typically these sorts of things have horrendous accessibility and
make the code more complex.
--
David
On Fri, 4 Nov 2022 at 02:17, Vasanth Mohan wrote:
> Hello,
>
> When there are multipl
This is a separate issue.
David
On Tue, 22 Nov 2022 at 04:42, Gagan Deep
wrote:
> Hello everyone!
>
> In my project, I have created a model (Token) which uses a custom primary
> key (i.e. it uses a field defined by the model for the primary key instead
> of using "id").
n (only tested on
Postgres).
Anyway, best of luck!
David
On Tue, 28 Mar 2023 at 00:57, Akash Sen wrote:
> Hello everyone,
> I’ve started this discussion to get feedback for my proposal for the
> project: Database-level Cascades Functionality to Django ORM. I have never
> contrib
>
> Thank you for your suggestion and nice implementation example. I would try
> to include that approach too.
>
No, that was just an example of a workaround without any of the benefits of
Django's emulation – the presence of a workaround often goes into
determining whether it's worth working on a
/instances/#django.db.models.Model.get_FOO_display
Kind regards,
David
On Wed, 5 Apr 2023 at 09:10, 'Ibrahim Abou Elenein' via Django developers
(Contributions to Django itself) wrote:
> Dear All,
>
> I am writing to report an issue I encountered while working with Django
> admin. I ha
At this point I'll let others chime in with their opinion on whether this
is something that needs to change because:
1. I rarely use admin
2. I've never really had the need to override a choice's display over
those supplied via `choices`
:)
On Wed, 5 Apr 2023 at 19:05, 'Ibrahim Abou Ele
t;https://github.com/shangxiao/stupid-django-tricks/tree/master/column_check_constraints>
for some experimentation with this idea.
Cheers,
David
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" grou
kemigrations --update" again.
I do not think it's a bug in Django.
Cheers,
David
Le sam. 8 avr. 2023 à 16:50, Muhammad Juwaini Abdul Rahman <
juwa...@gmail.com> a écrit :
> Do you need that '--update' parameter?
>
> On Fri, 7 Apr 2023 at 05:57, Saifullah Sha
Hi Adam, Mariusz & Simon,
> The only thing I'm not a fan of in your proposal is repeating the field
name within the check expression, like "price" in
> ... 8< ...
> Perhaps we could support only a special name instead, like “self” or the
shorter “f”?
I was thinking the same thing +1 I wanted to
ols if some version detection was put in place?
There may be a few other interesting tidbits related to Django that I've
missed. Here are the updates for application developers:
https://docs.oracle.com/en/database/oracle/oracle-database/23/nfcoa/application-development.html
Cheers,
David
Hi Dipankar,
Not being rude but serious question: What's the latest front end
technology? :)
On Wed, 19 Apr 2023, 7:27 pm Dipankar, wrote:
> Is there any plan to replace Django's automatic admin interface with the
> latest front end technology?
> There are several packages available but what if
Looks like python-oracledb is making updates to be compatible with
23c:
https://python-oracledb.readthedocs.io/en/latest/release_notes.html#oracledb-1-3-1-tbd
1.3.1 isn't released yet but the fact that updates are being made so soon
is encouraging 🎉
On Monday, 17 April 2023 at 22:06:57 UTC+10
Hola
El vie, 28 de abr de 2023 12:02 p. m., natali...@gmail.com <
nataliabid...@gmail.com> escribió:
> Hello everyone!
>
> I'm conducting a PR cleanse crusade for the project, where I'll try move
> forward those PRs that still make sense or close them when appropriate.
> Were there other developm
Mariusz is a developer, so that's at least 1 developer's opinion :)
Unless anybody else pipes up to counter this I'd consider it to be a nice
solution.
On Monday, 19 June 2023 at 05:01:52 UTC+10 Mubarak Alrashidi wrote:
> Can we at least know what the developers think about it?
>
>
> On Sunday,
Sorry to clarify I intended to respond with "niche solution" not "nice
solution" lol. I didn't realise the phone's autocomplete had done that.
On Monday, 19 June 2023 at 11:05:41 UTC+10 David Sanders wrote:
> Mariusz is a developer, so that's at least 1 dev
I posted a thread a while back about the latest version of Oracle 23c which
appears to add support for a few things that would fix some of the
workarounds we have in the ORM (eg boolean expressions). I know dropping
19c is a long way off but at least the future is looking brighter 🌟
On Wed, 9 Aug
json_value()`.
So this will work:
`Study.objects.filter(study_data__protocol__general__program_name__in=(Value("Program1",
output_field=JSONField()), ...))`
Regards
David
On Thursday, 26 October 2023 at 03:39:08 UTC+11 Nitin Chaudhary wrote:
> Hi
> I recently came across a very interesting scena
Hi Everyone,
I'm excited to propose the integration of SyncChatRoom, a real-time chat
functionality, into the Django framework. SyncChatRoom aims to provide
native support for WebSocket communication, making it easier for developers
to implement real-time chat features in their Django applicati
share any
further thoughts or ideas you may have.
Best regards,
David Ansa
On Friday, February 16, 2024 at 5:52:53 PM UTC+1 Fawemimo Owolabi wrote:
> I really support these motions, it really sound great but it will be best
> to used as a third-party package, also for drf as wel
Define TIME_INPUT_FORMATS in your local formats.py setup as per:
https://docs.djangoproject.com/en/5.0/topics/i18n/formatting/#creating-custom-format-files
On Tue, 5 Mar 2024 at 18:43, Arthur Pemberton wrote:
> The documentation (
> https://docs.djangoproject.com/en/5.0/ref/forms/fields/#timefie
101 - 200 of 807 matches
Mail list logo
