Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Possible Bug: Can not find timezone Northwest Time Border M�xico

See original GitHub issue

grass78\\Python37\\lib\\site-packages\\tzlocal\\win32.py\", line 79, in get_localzone_name
raise pytz.UnknownTimeZoneError('Can not find timezone ' + tzkeyname)
pytz.exceptions.UnknownTimeZoneError: 'Can not find timezone Northwest Time Border M�xico'"
"python: exited with code 1"

Not sure if this is an issue with the Windows installation reporting something strange, Python 3.7, or tzlocal not having this zone.

Looking at the IANA tzdata packages, this is indeed not a real Time Zone for Mexico, as IANA only identifies three zones:
Baja California Norte (the Mexico/BajaNorte TZ) Baja California Sur, Nayarit, Sinaloa and Sonora (the Mexico/BajaSur TZ) The rest of the country (the Mexico/General TZ)

Issue Analytics

State:
Created 2 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

regebrocommented, Oct 3, 2021

No, I don’t think they have configured it like that, I think the control panel gets nonsense configuration and probably shows the first or the last entry in the list as a result. This increases the likelihood that setting it to the correct timezone will fix the problem.

1reaction

regebrocommented, Oct 2, 2021

Correct, the timezone “Northwest Time Border Mexico” doesn’t exist, and in fact Google can’t find that phrase anywhere. Try re-configuring your timezone in the control panel. I suspect they mean the “Tiempo del Noroeste” zone, which in zoneinfo terms is called “America/Tijuana”, and in Windows should be called “Pacific Standard Time (Mexico)”.

It’s the same as US pacific time, so if you want you can try choosing that timezone instead, and it should work.