[Django] #35164: PermissionError: Permission denied: site-packages
Django
-------------------------------------+-------------------------------------
Reporter: milahu | Owner: nobody
Type: Bug | Status: new
Component: Database | Version: 5.0
layer (models, ORM) |
Severity: Normal | Keywords: database migrations
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
continue https://github.com/django/django/pull/17816
currently, django is trying to write database migration files
to the path of the app based on django
apps based on django can be installed in read-only paths
and then, django should not throw a fatal error
site-packages should be treated as read-only
runtime state belongs to $HOME/.cache/
felixxm has no interest in supporting this use case
i have no time for pointless discussions about obvious bugs
so "let someone else solve this problem"...
--
Ticket URL: <https://code.djangoproject.com/ticket/35164>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
Reporter: milahu | Owner: nobody
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: database migrations | Triage Stage:
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* status: new => closed
* resolution: => invalid
Comment:
Again, it is an issue in a 3rd party packages missed including migrations
for some model changes. You should report this to their issue tracker.
--
Ticket URL: <https://code.djangoproject.com/ticket/35164#comment:1>
Django
-------------------------------------+-------------------------------------
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
-------------------------------------+-------------------------------------
> felixxm has no interest in supporting this use case i have no time for
pointless discussions about obvious bugs so "let someone else solve this
problem"...
If `makemigrations` is attempting to generate migrations for packages
installed in your environment it's a symptom of a large problem and thus
it doesn't justify the patch you're proposing.
Mariusz is rightfully doing so and pointed you in the right direction.
Please take a moment to introspect your approach in suggesting changes
without providing details on how to reproduce your problem. These are not
pointless discussions and you should expect to engage in such talks if you
expect maintainers to consider your changes for inclusion and maintenance
for the years to come.
--
Ticket URL: <https://code.djangoproject.com/ticket/35164#comment:2>
Django
-------------------------------------+-------------------------------------
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
-------------------------------------+-------------------------------------
> 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
-------------------------------------+-------------------------------------
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
-------------------------------------+-------------------------------------
Dear milahu,
As mentioned by two Django maintainers, your use case is not supported by
Django: having 3rd party apps installed as dependencies and then modified
locally producing alterations that require new migrations is an anti-
pattern. You are, of course, free to make the decision of continuing doing
so, but please be mindful that Django will not include fixes for these
cases because it's not an usage pattern that we want to encourage.
If you need to modify a 3rd party app generating the need of new
migrations, the recommended path forward is to either reach out to the 3rd
party app maintainers, or fork the library if you have the permissions to
do so and make a new release of the library including the migration, so
it's installed in your dev environment with a clean and complete state.
If you still have questions, the best place to get more answers to your
issue is using any of the user support channels from
[https://docs.djangoproject.com/en/dev/faq/help/#how-do-i-do-x-why-
doesn-t-y-work-where-can-i-go-to-get-help this link].
--
Ticket URL: <https://code.djangoproject.com/ticket/35164#comment:4>