#7052: auth fixture fails to import when running test server
------------------------------------+---------------------------------------
Reporter: jb0t | Owner: nobody
Status: new | Milestone:
Component: Serialization | Version: SVN
Resolution: | Keywords: auth_permission
auth_content fixture import
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Comment (by shai):
Replying to [comment:13 russellm]:
>
> I have an idea how the solution will work, and I've articulated it
before. All I need is the time to implement it. Implementing a problematic
workaround will only serve to consume time that could be spent fixing the
problem.
I must be missing something; with this workaround, I haven't asked you, or
anyone else, to implement anything -- it's just a way for a substantial
part of the developers to solve their day-to-day problems, until a real
fix is done.
>
> > > you have just created a global namespace
> >
> > Em, no. content_types did that. And while it did take care to avoid
clashes, it didn't make the namespace properly (reproducibly)
serializable. I'm just taking the other side of the trade-off -- clash
avoidance responsibility to the user, in return for reproducible
serializability.
>
> content_types namespaces are currently global in the per-app sense. This
proposal makes them global in the 'whole globe' sense.
content_types ids are currently global in the global sense. That is what I
meant.
> Per-app, we can programatically avoiding collisions. We can't do that
over the entire globe without the IANA or something similar.
Yes, I agreed that people who build their apps to be used as components
shouldn't be doing this. You're rejecting my suggestion on the grounds
that it doesn't solve the problem for all django apps, ignoring the fact
that it is a good workaround for many. My own application, which triggered
my need for this, is not going to be part of any system but my own; this
is the situation with a substantial part of the django apps -- where IANA
etc. are simply not an issue.
Again: I'm not asking you to do anything about this workaround except,
well, stop opposing it, or explain why it's bad *for a single-system app*.
--
Ticket URL: <http://code.djangoproject.com/ticket/7052#comment:14>
Django Code <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
