starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

[PR #11278] [CLOSED] pin pytz version to 2022.7 in requirements.txt #13765

New Issue
Closed
opened 2025-12-29 23:20:40 +01:00 by adam · 0 comments
adam commented 2025-12-29 23:20:40 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/netbox-community/netbox/pull/11278
Author: @nicoovh
Created: 12/21/2022
Status: ❌ Closed

Base: develop ← Head: patch-1

📝 Commits (1)

  • 7d8e7cc pin pytz version to 2022.7 in requirements.txt

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 requirements.txt (+1 -0)

📄 Description

Fixes: #11277

When pytz/tzdata release a new version together, if both are not pinned together, we end up with a mixed, non compatible versions. It happens this month with netbox version 3.3.8, because a fresh install would get tzdata==2022.6, as pinned in requirements.txt, and pytz==2022.7.

Which may lead to following error:

zoneinfo._common.ZoneInfoNotFoundError: 'No time zone found with key America/Ciudad_Juarez'

I suggest to pin both versions in the requirements.txt file.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/netbox-community/netbox/pull/11278 **Author:** [@nicoovh](https://github.com/nicoovh) **Created:** 12/21/2022 **Status:** ❌ Closed **Base:** `develop` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`7d8e7cc`](https://github.com/netbox-community/netbox/commit/7d8e7ccec1db163ae010e7e9baea7c1f398ba4ce) pin pytz version to 2022.7 in requirements.txt ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `requirements.txt` (+1 -0) </details> ### 📄 Description ### Fixes: #11277 When pytz/tzdata release a new version together, if both are not pinned together, we end up with a mixed, non compatible versions. It happens this month with netbox version 3.3.8, because a fresh install would get ``tzdata==2022.6``, as pinned in requirements.txt, and ``pytz==2022.7``. Which may lead to following error: ``zoneinfo._common.ZoneInfoNotFoundError: 'No time zone found with key America/Ciudad_Juarez'`` I suggest to pin both versions in the requirements.txt file. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2025-12-29 23:20:40 +01:00
adam closed this issue 2025-12-29 23:20:40 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#13765
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?