Nova/PyWebServer
1
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases 10 Wiki Activity

Migration from PWS/1.4.0 / Amethyst-b0001-0038 to Amethyst-b0039+ #7

New Issue
Open
opened 2026-03-02 23:18:35 +01:00 by Nova · 2 comments
Nova commented 2026-03-02 23:18:35 +01:00
Owner
Copy Link

Currently people running PyWebServer 1.4.0 or Amethyst beta 0001 to 0038 cannot just upgrade to the latest release (Amethyst-b0039+) without some extra help. In here I plan to track what issues arise from migration and how to solve them.

Currently people running PyWebServer 1.4.0 or Amethyst beta 0001 to 0038 cannot just upgrade to the latest release (Amethyst-b0039+) without some extra help. In here I plan to track what issues arise from migration and how to solve them.
Nova added the Compat/Breaking
Priority
Critical
 labels 2026-03-02 23:18:35 +01:00
Nova self-assigned this 2026-03-02 23:18:35 +01:00
Nova commented 2026-03-02 23:21:36 +01:00
Author
Owner
Copy Link

Due to the extreme configuration overhaul, the configuration is the main key of focus here, if unexpected behaviour that a user might have based their logic around has been fixed in the latest version, I will try to find a way to make stuff still work, but it is significantly lower priority compared to configuration issues.

Due to the extreme configuration overhaul, the configuration is the main key of focus here, if unexpected behaviour that a user might have based their logic around has been fixed in the latest version, I will try to find a way to make stuff still work, but it is significantly lower priority compared to configuration issues.
Nova commented 2026-03-02 23:22:19 +01:00
Author
Owner
Copy Link

One note is that pywebsrv.conf (the old configuration file) is still used for some queries, this will later be removed, don't base any logic on it!

One note is that `pywebsrv.conf` (the old configuration file) is still used for some queries, this will later be removed, don't base any logic on it!
Sign in to join this conversation.
2.0
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label Compat/Breaking
Priority
Critical
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Nova
No Assignees Nova
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Nova/PyWebServer#7
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?