Multiple zip codes in one locality about django-address HOT 4 CLOSED

Seems related to an issue I created a while ago, although that was more of a lookup issue, and you're pointing out a design issue. #34 (comment)

A less related zipcode issue: Localities are assigned the wrong zip/postal code #56

from django-address.

PR #41 will ensure a unique locality will be generated for each combination of locality name and zip code.

from django-address.

I'll actually take this a bit further and say that postal codes should not be tied to locality at all. Postal codes are national constructs that overlay with the boundaries of metro areas.

The side effect here is that a large city like Los Angeles has > 900 zip codes which means one would end up with potentially hundreds of "Los Angeles, California, USA" entries just for separate zip codes - but the zips are inside Los Angeles, not the other way around - one city, many postal codes.

It seems like postal code should really just be an attribute of 'Address'. Or am I missing something about the design approach?

from django-address.

While the original issue described by @cassidylaidlaw has been resolved in pull/41, @explody 's structural question is still valid.

I'm closing this issue as completed, however I have made a note about considering refactoring postal code out of locality in a future release here. Please see #98 for updates on django-address

from django-address.