#35164: PermissionError: Permission denied: site-packages
-------------------------------------+-------------------------------------
Reporter: milahu | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: database migrations | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by milahu):
> If makemigrations is attempting to generate migrations for packages
installed in your environment it's a symptom of a large problem
https://github.com/django/django/pull/17816#issuecomment-1925362445
>> It seems that one of your 3rd party packages missed including
migrations for some model changes
>
>yes, i modified the app, but i did not include the new migration file
>
>django throwing a fatal error here is "too much"
>
>django should store the new migration file somewhere, where the user can
find it
>show an info (or warning) and continue running the app
>
>then, what the user does with that new migration file, is his business
--
Ticket URL: <https://code.djangoproject.com/ticket/35164#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018d70e1d073-1125d05d-fc0e-404b-8a78-a7de886c7950-000000%40eu-central-1.amazonses.com.
