Thank you Barhamou for raising the question here and starting the
discussion.
I agree with Adrian that this feels like a pretty niche use case.
Depending on the needs, other possible implementations might include:
4. A form field mapping to multiple model fields
5. A custom queryset/manager that
Hello Everyone , myself Arpita Srivastava a pre final year computer science
student.
I want to contribute in GSoC 2023 as my skill sets include python , Django.
So I have chosen Django as the organization to contribute in.
I was hoping If I could get some help from the Django & python community
Hello all, please take a look at
https://docs.djangoproject.com/en/dev/internals/contributing/new-contributors/
to find advice for new contributors.
On Tuesday, January 10, 2023 at 11:26:12 AM UTC-5 arpitasriv...@gmail.com
wrote:
> Hello Everyone , myself Arpita Srivastava a pre final year com
Hi, I'm glad I contributed to something. I understand your point of view.
I'm new and looking for an interesting topic to work on in my spare time.
I don't want to waste my energy on a feature that doesn't get a lot of
support.
However, if this ticket still exists, there must be a problem somewh
I was just looking at custom management commands (Django 3.2) and noted
that the error handling for a subparser didn't match the Django behaviour
without some extra, undocumented work.
If my Command subclass implements the following:
def add_arguments(self, parser):
subparsers = pa
