south confused by similar app names

[msoulier@…]

I have two apps in separate projects, where one project is common code for two separate interfaces.

webproxy.main
proxycore.main

If I tell south to do schema migration for proxy.main, it finds proxycore.main first and doesn't find proxy.main at all.

It should be able to tell the difference.

(msl9.4)msoulier@espresso:...b/django/webproxy$ python manage.py schemamigration webproxy.main --auto

+ Added model main.UserProfile?
+ Added model main.ProxyApp?
+ Added model main.ProxyPermission?

Created 0002_autoadd_userprofileadd_proxyappadd_proxypermission.py. You can now apply this migration with: ./manage.py migrate webproxy.main

Note, those models are from proxycore.main

(msl9.4)msoulier@espresso:...b/django/webproxy$ python manage.py schemamigration proxycore.main --auto
Nothing seems to have changed.

So now I must rename proxycore.main to something else, like proxycore.core, as a workaround.

[anonymous]

Hi, there's an initial patch to make South aware of multiple apps w/ the same name (for now only tested with schemamigration --initial command and migrate command)

Regards,
yedpodtrzitko

[andrew]

As I've said before, this is a bug in Django, not South - until Django lands the new app loading branch which distinguishes apps by more than label, South will act like this (much like the built-in Django commands like ./manage.py sql)

[yedpodtrzitko]

Did not see any statement about this bug, but I agree - creating this patch was really just hacking around Django.