hello I'm new to Django Developer anyone can share learning document?
On Mon, Dec 9, 2024 at 5:03 PM Arthur Pemberton wrote:
> Adam,
>
> Up until now, I've only been reading the test. Now that I actually tried
> running the test, it does not get discovered by the testing system (without
> modifi
Adam,
Up until now, I've only been reading the test. Now that I actually tried
running the test, it does not get discovered by the testing system (without
modifications to test_input_formats.py) and when I do get the test to run,
it fails.
I used tag "5.1.4" to get the unit tests.
Arthur
On
As further follow up on this, as far as I can tell, the relevant unit test
does not run, seemingly due to the use of `translation.override(None)`
Removing, that, and running the test `./runtests.py
forms_tests.tests.test_input_formats.CustomTimeInputFormatsTests.test_timeField`
results in the
To simplify things further, within a view:
TIME_INPUT_FORMATS = ['%H:%M:%S', '%H:%M:%S.%f', '%H:%M', '%I:%M %p']
and
forms.TimeField.input_formats = ['%H:%M:%S', '%H:%M:%S.%f', '%H:%M']
On Sun, Dec 8, 2024 at 9:55 AM Arthur Pemberton wrote:
> I finally got back to this.
>
> I have a failing m
I finally got back to this.
I have a failing minimal project (not test) that
demonstrates TIME_INPUT_FORMATS not being respected:
https://github.com/pembo13/dateentry
In the example, the form should be valid, if TIME_INPUT_FORMATS worked as
documented.
I _think_ there's something about how the u
Thank you 🙏🏿
On Sun, May 19, 2024, 1:44 AM Arthur Pemberton wrote:
> I haven't yet checked the tests thoroughly enough to determine why things
> didn't work for me in practice. I do know they didn't work. And I do see
> that the tests pass. But I suspect that the tests may not be fully
> mimicki
I haven't yet checked the tests thoroughly enough to determine why things
didn't work for me in practice. I do know they didn't work. And I do see
that the tests pass. But I suspect that the tests may not be fully
mimicking the read-world use case in this scenario.
I'll return here once I have som
USE_I18N does not disable localization, but internationalization. USE_L10N was
the setting to enable/disable localization, but it was deprecated in Django
4.0: https://docs.djangoproject.com/en/4.0/releases/4.0/#localization . It was
removed completely in Django 5.0, in this commit:
https://git
Thanks, I'll look into that. But does that mean that
settings.TIME_INPUT_FORMATS no longer has any use? I don't see any logic
flows that lead to it being used.
On Tue, Mar 5, 2024 at 3:00 AM David Sanders
wrote:
> Define TIME_INPUT_FORMATS in your local formats.py setup as per:
> https://docs.dj
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
10 matches
Mail list logo
