o ["Faux parser object that will ferry our arguments into options.cCs ||_dS©N)Úcommand)Úselfr©rúA/var/www/html/kck/venv/lib/python3.10/site-packages/django_six.pyÚ__init__0s zProxyParser.__init__cOs |jjt|i|¤Žf7_dSr )rÚ option_listr)rÚargsÚkwargsrrrÚ add_argument3s zProxyParser.add_argumentN)Ú__name__Ú __module__Ú __qualname__Ú__doc__rrrrrrr -s r cs eZdZdZ‡fdd„Z‡ZS)ÚCompatibilityBaseCommandavProvides a compatibility between optparse and argparse transition. Starting in Django 1.8, argparse is used. In Django 1.9, optparse support will be removed. For optparse, you append to the option_list class attribute. For argparse, you must define add_arguments(self, parser). BaseCommand uses the presence of option_list to decide what course to take. csHtjdkrt|dƒrtj|_t|ƒ}| |¡tt|ƒj |i|¤ŽdS)N)ééÚ add_arguments) ÚdjangoÚVERSIONÚhasattrrrr rÚsuperrr)rrrÚparser©Ú __class__rrr?s  z!CompatibilityBaseCommand.__init__)rrrrrÚ __classcell__rrr$rr7src@óeZdZdZdS)ÚCompatibilityAppCommandz?AppCommand is a BaseCommand sub-class without its own __init__.N©rrrrrrrrr(Gór(c@r')ÚCompatibilityLabelCommandzALabelCommand is a BaseCommand sub-class without its own __init__.Nr)rrrrr+Kr*r+)ÚoptparserrÚdjango.core.management.baserrrrÚ django.dbrrÚ ImportErrorÚdjango.utils.deprecationr ÚobjectÚdjango.db.models.queryr ÚSupport_ValuesQuerySetÚtyper ÚSupport_ValuesListQuerySetr rr(r+rrrrÚs@  ÿ ý  þ  þ