+ S2MigrationQuestioner.ask_initial..7s$Vi CU,1::e,,is(()rrget_app_config LookupErrorr getrmigrations_modulelabel importlib import_modulegetattroslistdirpathdirnamerhasattrlenrlistany ImportError)r app_label app_configmigrations_import_path_r# filenamess&& rrMigrationQuestioner.ask_initialsr ++ +  ;,,Y7J%4$E$EjFVFV$W! ! )==$$]E: : W ) 7 78N O (*d;;JJrww7H7Q7Q'RS *J77(112Q6 JJt,=,F,F'G'JK sViVssV VsV VsViVVV V# ;==$$]E: : ; ;==$$]E: : ;s#E5-F"5'FF"'G  G c R#)#Adding a NOT NULL field to a model.Nr field_name model_names&&&rask_not_null_addition)MigrationQuestioner.ask_not_null_addition9rc R#)"Changing a NULL field to NOT NULL.Nr9r:s&&&rask_not_null_alteration+MigrationQuestioner.ask_not_null_alteration>r?rc :VPPRR4#)Was this field really renamed? ask_renameFr r")rr<old_namenew_namefield_instances&&&&&rrFMigrationQuestioner.ask_renameCs}}  u55rc :VPPRR4#)Was this model really renamed?ask_rename_modelFrG)rold_model_statenew_model_states&&&rrN$MigrationQuestioner.ask_rename_modelGs}}  !3U;;rc :VPPRR4#)z)Should these migrations really be merged? ask_mergeFrGrr1s&&rrSMigrationQuestioner.ask_mergeKs}}  e44rc R#)(Adding an auto_now_add field to a model.Nr9r:s&&&rask_auto_now_add_addition-MigrationQuestioner.ask_auto_now_add_additionOr?rc R#).Adding a unique field with a callable default.Nr9r:s&&&r$ask_unique_callable_default_addition8MigrationQuestioner.ask_unique_callable_default_additionTr?r)r rr)NNN)__name__ __module__ __qualname____firstlineno____doc__rrr=rBrFrNrSrXr\__static_attributes____classdictcell__) __classdict__s@rr r s=  W<  6<5 rr czaa]tRt^ZtoR V3RlltRRltRtRRltRtRt Rt Rt R t R t R tR tVtV;t#)InteractiveMigrationQuestionercz<\SV`WVR7T;'g\\P4VnR#)r rrN)superrrsysstdout prompt_output)rr rrrm __class__s&&&&&rr'InteractiveMigrationQuestioner.__init__[s7 g  +GGmCJJ.Grc@VPPV R2RR7\4pV'gVeV#V'dV^,P4R9d*VPPRRR7\4pKMV^,P4R8H#) endingynzPlease answer yes or no: y)rmwriteinputlower)rquestiondefaultresults&&& r_boolean_input-InteractiveMigrationQuestioner._boolean_inputcs   H:Q ;'-NF1IOO-T9    $ $%@ $ LWFay C''rc4VPPV 4\V4F/wr4VPPRV^,: RV: 24K1 VPPRRR7\4p\ V4p^Tu;8d\ V48:dV#MVPPRRR7KT \ dL,\d5TPPR4\P!^4Lii;i)rqz) zSelect an option: rrrs Cancelled.zPlease select a valid option: ) rmrw enumeraterxintr- ValueErrorKeyboardInterruptrkexit)rrzchoicesichoicer|values&&& r _choice_input,InteractiveMigrationQuestioner._choice_inputms   H:/"7+IA    $ $!a%%%@ A,   !5b A !F u,G , L-    $ $%Eb $ Q $ ""((8  s:C DD"2DDc |VPPR4V'd VPPRV R24VPPR4VPPR4V'dRPV4pMRpVPPVRR 7\4pX'g V'dTpV'gVPPR 4K|VR 8Xd\ P !^4K\V/R \R\/4# \d5TPPR 4\ P !^4Li;i \dApTPPTPP RT 24Rp?EK=Rp?ii;i)z Prompt for a default value. The ``default`` argument allows providing a custom default value (as a string) which will be shown to the user and used as the return value if the user doesn't provide any other input. z/Please enter the default value as valid Python.zAccept the default 'z/' by pressing 'Enter' or provide another value.zxThe datetime and django.utils.timezone modules are available, so it is possible to provide e.g. timezone.now as a value.zType 'exit' to exit this promptz[default: {}] >>> z>>> rrrsrz;Please enter some code, or 'exit' (without quotes) to exit.rdatetimerz: N) rmrwformatrxrrkrevalrr Exceptionrnr^)rr{promptcodees&& r _ask_default+InteractiveMigrationQuestioner._ask_defaults|   !RS     $ $&wi0)*     F    !BC-44W=    $ $VB $ 7 wG""((Q Mb:xX*VWW% ""((8  !M&&,, 0D0D/ERs-KLLMs*4 D.E0.*>@T@TU V   rc&VPRR4#)zH Merging will only work if the operations printed above do not conflict Fz Merging will only work if the operations printed above do not conflict with each other (working on different fields or models) Should these migration branches be merged? [y/N])r}rTs&&rrS(InteractiveMigrationQuestioner.ask_merges "" A    rc VP'gMVPRV RV R2RR.4pV^8Xd\P!^4R#VP RR7#R#) rWz#It is impossible to add the field 'z' with 'auto_now_add=True' to zf without providing a default. This is because the database needs something to populate existing rows. zDProvide a one-off default now which will be set on all existing rowsrz timezone.now)r{Nrrs&&& rrX8InteractiveMigrationQuestioner.ask_auto_now_add_additionsv|||''5j\B**46,- $L F{ (((@@rc VP'gG\4pVPRV RV R2RV R2R.4pV^8Xd\P!^4R#)r[z!Callable default on unique field .zO will not generate unique values upon migrating. Please choose how to proceed: zContinue making this migration as the first step in writing a manual migration to generate unique values described here: https://docs.djangoproject.com/en/z=/howto/writing-migrations/#migrations-that-add-unique-fields.z)Quit and edit field options in models.py.N)rrrrkr)rr;r<versionrs&&& rr\CInteractiveMigrationQuestioner.ask_unique_callable_default_additionsw|||&(G''3J>A  HH*\*=M(!  rcXVPVVR4\P!^4R#)zIit is impossible to add a non-nullable field without specifying a defaultNrrkrr:s&&&rr=7NonInteractiveMigrationQuestioner.ask_not_null_additionAs( ""     rc>VPRV RV R24\#)rrz8' given a default of NOT PROVIDED and must be corrected.)rrr:s&&&rrB9NonInteractiveMigrationQuestioner.ask_not_null_alterationKs- j\j\:2 3 rcXVPVVR4\P!^4R#)zUit is impossible to add a field with 'auto_now_add=True' without specifying a defaultNrr:s&&&rrX;NonInteractiveMigrationQuestioner.ask_auto_now_add_additionSs( ""   #  r)rr)NNNN) r^r_r`rarrr=rBrXrcrdrrs@@rrr)s# rr)rr%r(rk django.appsrdjango.core.management.baserdjango.db.modelsr django.utilsrdjango.utils.versionrloaderrr rgrr9rrrsM 5)!1#HHVL%8L^2(;2r