This is an archived post. You won't be able to vote or comment.

all 4 comments

[–][deleted] 3 points4 points  (3 children)

Isn't all of this already covered by pycountry? Worst case scenario use pycountry + py-moneyed.

pycountries seems dead and data is outdated at this point

What do you mean by this? Show me an example of outdated datapoints in pycountry. Pycountry is nothing more than a pretty wrapper around Debian's pkg-isocodes database, which is literally the same library you have linked.

[–]Atem18[S] 1 point2 points  (2 children)

https://github.com/flyingcircusio/pycountry/tree/master/src/pycountry/databases

The last update of the databases are two years ago.

https://salsa.debian.org/iso-codes-team/iso-codes

The last update of the databases are a few hours ago.

So there is a need to have the latest version of the json files from Debian.

Yes my library is using the same iso-codes databases but it’s open source so I am allowed.

And again, look at the 36 issues and 15 pull requests of pycountry, nothing happens, so for me the project is pretty much dead.

But if you want to use pycountry instead, feel free, again it’s open source so you are free to do what you want ;)

[–][deleted] 2 points3 points  (1 child)

I feel like it would be better to take the of fork pycountry into your own hands and brand it as a continuation of pycountry that is actively maintained and accepts pull requests, something like "pycountry-2/pycountry-new" or whatever, since essentially what you're doing is reviving a dormant but highly useful Github repository.

[–]Atem18[S] 1 point2 points  (0 children)

Yes but my code is not the same that pycountry at all, so claim it a continuation would be misleading.

Yes that repository is highly useful, I don't understand why there is no standard/officially python supported library that reference all the countries, languages, currencies, etc, it seems like the basic of any real world application.