Re: Django t-shirt

2023-01-15 Thread 'Adam Johnson' via Django developers (Contributions to Django itself) 
There is a Django Threadless store where you can buy T-Shirts and other
merchandise, which all supports the DSF: https://django.threadless.com/

It’s linked from the fundraising page:
https://www.djangoproject.com/fundraising/

I have a Django phone case from there!

On Fri, Jan 13, 2023 at 11:44 AM Stephen Wolff 
wrote:

> Hi there,
>
> A few Django versions ago (1.7 and maybe 1.8?!), t-shirts were produced
> and sold (i guess for fundraising purposes?).
>
> Just wondering given the forthcoming LTS is 4.2, which has similarities to
> Douglas Adams's answer to the life, universe and everything, whether a new
> t-shirt could be produced?
>
> Yours hopefully,
>
> Stephen
>
> --
> 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 to django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/7570a944-3822-4493-acf0-4510c24e7b8bn%40googlegroups.com
> 
> .
>

-- 
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 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM2jQx2RTyDktvi%2BTCMa%3D4PR43SXPpwxv7V9A8bL-z-hEA%40mail.gmail.com.

Re: Django accounting software.

2023-01-15 Thread 'Adam Johnson' via Django developers (Contributions to Django itself) 
Hi!

I think you've found the wrong mailing list for this post. This mailing
list is for discussing 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 your support query with their limited time and energy.

For support, please follow the "Getting Help" page:
https://docs.djangoproject.com/en/stable/faq/help/ . This will help you
find people who are willing to support you, and to ask your question in a
way that makes it easy for them to answer.

Thanks for your understanding and all the best,

Adam

On Thu, Jan 12, 2023 at 8:07 PM KEMAL TK.  wrote:

> It will be used to track customer, inventory, financial affairs.
>
> Django accounting software.
> There are examples on githup.
> perfexcrm this application can be referenced.
>
> --
> 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 to django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/57196a4d-e076-4b50-bbea-37826aee7953n%40googlegroups.com
> 
> .
>

-- 
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 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM3XsCfnTKoWvVHfVezq%2B%3DFAQn%3DoBhjateR-dyP_8JWEfg%40mail.gmail.com.

Re: Subparsers for management commands

2023-01-15 Thread 'Adam Johnson' via Django developers (Contributions to Django itself) 
Hi Mark

I agree that subparsers should use the same error formatting.

After looking at the problem a bit more, I found a solution to pass
called_from_command_line through to subparsers by changing CommandParser. I
filed a ticket and a PR: https://code.djangoproject.com/ticket/34259#ticket

Thanks,

Adam

On Wed, Jan 11, 2023 at 2:02 AM Mark Gregson  wrote:

> 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 = parser.add_subparsers()
> sub = subparsers.add_parser("thing")
>
> errors raised by the subparser, eg, for missing arguments, result in the
> command exiting with a stack trace.  Normal behaviour in Django when a
> command is called from the command line is a nice error message and I
> expect subparsers to act the same way.
>
> The error handling behaviour depends on the
> parser.called_from_command_line attribute which must be set manually for
> subparsers to achieve the same, eg:
>
> sub = subparsers.add_parser("thing", called_from_command_line=
> parser.called_from_command_line)
>
> I'd propose adding a little documentation about this argument with an
> example so that the next me doesn't need to hunt through the code to
> understand what's happening.
>
> Another option would be to add a convenience method that would ensure
> called_from_command_line is set correctly, eg,
>
> class CommandParser:
> def add_subparser(self, subparsers, name, **kwargs):
> kwargs.setdefault(
> "called_from_command_line",
> self.called_from_command_line
> )
> return subparsers.add_parser(name, **kwargs)
>
> which would save repetition but would still require command authors have
> some special Django knowledge so I'd question whether it's worthwhile.
>
> I'm happy to contribute if advised on the preferred option.
>
> Cheers
> Mark
>
> --
> 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 to django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/06855745-cff7-4474-8538-2589d0a0a650n%40googlegroups.com
> 
> .
>

-- 
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 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM2_hVQsPGSBu2Vg9iJ3QpJ%2BCo7TJk61L-Mncp4%3DykgeLw%40mail.gmail.com.

Re: Django t-shirt

2023-01-15 Thread Stephen Wolff 
Awesome thanksSent from a mobile device!On 15 Jan 2023, at 08:03, 'Adam Johnson' via Django developers  (Contributions to Django itself)  wrote:There is a Django Threadless store where you can buy T-Shirts and other merchandise, which all supports the DSF: https://django.threadless.com/It’s linked from the fundraising page: https://www.djangoproject.com/fundraising/I have a Django phone case from there!On Fri, Jan 13, 2023 at 11:44 AM Stephen Wolff  wrote:Hi there,A few Django versions ago (1.7 and maybe 1.8?!), t-shirts were produced and sold (i guess for fundraising purposes?).Just wondering given the forthcoming LTS is 4.2, which has similarities to Douglas Adams's answer to the life, universe and everything, whether a new t-shirt could be produced?Yours hopefully,Stephen



-- 
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 to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/7570a944-3822-4493-acf0-4510c24e7b8bn%40googlegroups.com.




-- 
You received this message because you are subscribed to a topic in the Google Groups "Django developers  (Contributions to Django itself)" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-developers/eM5LaDD8NCQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM2jQx2RTyDktvi%2BTCMa%3D4PR43SXPpwxv7V9A8bL-z-hEA%40mail.gmail.com.




-- 
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 to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/645AD2FF-F08E-4208-99DE-EAFC69E9495B%40gmail.com.

Re: Subparsers for management commands

2023-01-15 Thread Mark Gregson 

Thanks Adam, nice solution.
On Sunday, 15 January 2023 at 19:23:56 UTC+10 Adam Johnson wrote:

> Hi Mark
>
> I agree that subparsers should use the same error formatting.
>
> After looking at the problem a bit more, I found a solution to pass 
> called_from_command_line through to subparsers by changing CommandParser. 
> I filed a ticket and a PR: 
> https://code.djangoproject.com/ticket/34259#ticket
>
> Thanks,
>
> Adam
>
> On Wed, Jan 11, 2023 at 2:02 AM Mark Gregson  wrote:
>
>> 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 = parser.add_subparsers()
>> sub = subparsers.add_parser("thing")
>>
>> errors raised by the subparser, eg, for missing arguments, result in the 
>> command exiting with a stack trace.  Normal behaviour in Django when a 
>> command is called from the command line is a nice error message and I 
>> expect subparsers to act the same way.
>>
>> The error handling behaviour depends on the 
>> parser.called_from_command_line attribute which must be set manually for 
>> subparsers to achieve the same, eg: 
>>
>> sub = subparsers.add_parser("thing", called_from_command_line=
>> parser.called_from_command_line) 
>>
>> I'd propose adding a little documentation about this argument with an 
>> example so that the next me doesn't need to hunt through the code to 
>> understand what's happening.
>>
>> Another option would be to add a convenience method that would ensure  
>> called_from_command_line is set correctly, eg, 
>>
>> class CommandParser:
>> def add_subparser(self, subparsers, name, **kwargs):
>> kwargs.setdefault(
>> "called_from_command_line", 
>> self.called_from_command_line
>> )
>> return subparsers.add_parser(name, **kwargs)
>>
>> which would save repetition but would still require command authors have 
>> some special Django knowledge so I'd question whether it's worthwhile.
>>
>> I'm happy to contribute if advised on the preferred option.
>>
>> Cheers
>> Mark
>>
>> -- 
>> 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 to django-develop...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-developers/06855745-cff7-4474-8538-2589d0a0a650n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/662cf56f-2980-4d6f-84e3-53923ceef734n%40googlegroups.com.