Re: [Django] #23309: call_commands laks some code to act like as run_from_argv

#23309: call_commands laks some code to act like as run_from_argv -+- Reporter: rsalmaso |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #23305: Models that are imported on app's import time are invisible to makemigrations when the application is relabeld

#23305: Models that are imported on app's import time are invisible to makemigrations when the application is relabeld +-- Reporter: rafalp |Owner: nobody Type: Bug |

Re: [Django] #23308: Running a migration fails when adding a foreign key to another app

#23308: Running a migration fails when adding a foreign key to another app ---+-- Reporter: amarsahinovic |Owner: nobody Type: Bug| Status: new Component: Migrat

Re: [Django] #23307: max_num limits total number of forms, not empty forms

#23307: max_num limits total number of forms, not empty forms -+- Reporter: velle|Owner: nobody Type: | Status: new Cleanup/optimiza

Re: [Django] #23307: max_num limits total number of forms, not empty forms

#23307: max_num limits total number of forms, not empty forms -+- Reporter: velle|Owner: nobody Type: | Status: new Cleanup/optimiza

Re: [Django] #23302: Cannot give a name to a migration from command line

#23302: Cannot give a name to a migration from command line -+ Reporter: rsalmaso |Owner: nobody Type: New feature | Status: new Component: Migrations |

Re: [Django] #23302: Cannot give a name to a migration from command line

#23302: Cannot give a name to a migration from command line ---+ Reporter: rsalmaso |Owner: nobody Type: Uncategorized | Status: new Component: Migrations |

Re: [Django] #23305: Models that are imported on app's import time are invisible to makemigrations when the application is relabeld

#23305: Models that are imported on app's import time are invisible to makemigrations when the application is relabeld -+-- Reporter: rafalp |Owner: nobody Type: Bug |

Re: [Django] #22280: "Conflicting models in application" RuntimeError for same model with different paths

#22280: "Conflicting models in application" RuntimeError for same model with different paths ---+ Reporter: blueyed|Owner: nobody Type: Bug| Status:

Re: [Django] #10410: FileField saves one filename on disk and another on DB

#10410: FileField saves one filename on disk and another on DB -+- Reporter: Elland |Owner: peterbe Type: Uncategorized| Status: closed Component

Re: [Django] #23309: call_commands laks some code to act like as run_from_argv

#23309: call_commands laks some code to act like as run_from_argv -+- Reporter: rsalmaso |Owner: nobody Type: Uncategorized| Status: new Component:

[Django] #23309: call_commands laks some code to act like as run_from_argv

#23309: call_commands laks some code to act like as run_from_argv + Reporter: rsalmaso| Owner: nobody Type: Uncategorized | Status: new Component: Core (Management comma

[Django] #23308: Running a migration fails when adding a foreign key to another app

#23308: Running a migration fails when adding a foreign key to another app ---+-- Reporter: amarsahinovic | Owner: nobody Type: Bug| Status: new Component: Migrations |Version: 1.7-rc-2 Severi

[Django] #23307: max_num limits total number of forms, not empty forms

#23307: max_num limits total number of forms, not empty forms --+ Reporter: velle | Owner: nobody Type: Cleanup/optimization | Status: new Component: Documentation |Version: 1.4

Re: [Django] #23306: Cannot call a command with --name option

#23306: Cannot call a command with --name option -+- Reporter: rsalmaso |Owner: nobody Type: Uncategorized| Status: closed Component: Core (Manage

Re: [Django] #23306: Cannot call a command with --name option

#23306: Cannot call a command with --name option -+- Reporter: rsalmaso |Owner: nobody Type: Uncategorized| Status: closed Component: Core (Manage

Re: [Django] #23306: Cannot call a command with --name option

#23306: Cannot call a command with --name option -+- Reporter: rsalmaso |Owner: nobody Type: Uncategorized| Status: closed Component: Core (Manage

Re: [Django] #23292: ATOMIC_REQUESTS creates unnecessary database connections and transactions

#23292: ATOMIC_REQUESTS creates unnecessary database connections and transactions -+- Reporter: ijl |Owner: nobody Type: Bug | Status: c

Re: [Django] #22632: Spatial backend tests uses hardcoded set of backends

#22632: Spatial backend tests uses hardcoded set of backends --+ Reporter: jtiai |Owner: nobody Type: Cleanup/optimization | Status: new Component: G

Re: [Django] #23306: Cannot call a command with --name option

#23306: Cannot call a command with --name option -+- Reporter: rsalmaso |Owner: nobody Type: Uncategorized| Status: closed Component: Core (Manage

Re: [Django] #23306: Cannot call a command with --name option

#23306: Cannot call a command with --name option -+- Reporter: rsalmaso |Owner: nobody Type: Uncategorized| Status: new Component: Core (Managemen

Re: [Django] #23302: Cannot give a name to a migration from command line

#23302: Cannot give a name to a migration from command line ---+-- Reporter: rsalmaso |Owner: nobody Type: Uncategorized | Status: new Component: Migrations |

[Django] #23306: Cannot call a command with --name option

#23306: Cannot call a command with --name option + Reporter: rsalmaso| Owner: nobody Type: Uncategorized | Status: new Component: Core (Management commands) |Versio

Re: [Django] #22280: "Conflicting models in application" RuntimeError for same model with different paths

#22280: "Conflicting models in application" RuntimeError for same model with different paths ---+ Reporter: blueyed|Owner: nobody Type: Bug| Status:

Re: [Django] #23305: Models that are imported on app's import time are invisible to makemigrations when the application is relabeld

#23305: Models that are imported on app's import time are invisible to makemigrations when the application is relabeld -+-- Reporter: rafalp |Owner: nobody Type: Bug |

Re: [Django] #23305: Models that are imported on app's import time are invisible to makemigrations when the application is relabeld (was: Models that are imported on app's import time are invisible to

#23305: Models that are imported on app's import time are invisible to makemigrations when the application is relabeld -+-- Reporter: rafalp |Owner: nobody Type: Bug |

Re: [Django] #23305: Models that are imported on app's import time are invisible to makemigrations when the application is relabeld

#23305: Models that are imported on app's import time are invisible to makemigrations when the application is relabeld -+-- Reporter: rafalp |Owner: nobody Type: Bug |

Re: [Django] #23305: Models that are imported on app's import time are invisible to makemigrations

#23305: Models that are imported on app's import time are invisible to makemigrations -+-- Reporter: rafalp |Owner: nobody Type: Bug | Status: new C

Re: [Django] #23305: Models that are imported on app's import time are invisible to makemigrations

#23305: Models that are imported on app's import time are invisible to makemigrations -+-- Reporter: rafalp |Owner: nobody Type: Bug | Status: closed

Re: [Django] #23302: Cannot give a name to a migration from command line

#23302: Cannot give a name to a migration from command line ---+-- Reporter: rsalmaso |Owner: nobody Type: Uncategorized | Status: new Component: Migrations |