Skip to content
This repository has been archived by the owner on Sep 26, 2023. It is now read-only.

Upstream bug in django.channels vs Python 3.7.11 (3.7.14) #93

Open
radl97 opened this issue Sep 14, 2022 · 2 comments
Open

Upstream bug in django.channels vs Python 3.7.11 (3.7.14) #93

radl97 opened this issue Sep 14, 2022 · 2 comments

Comments

@radl97
Copy link
Collaborator

radl97 commented Sep 14, 2022 •
edited
Loading

https://github[.]com/django/channels/issues/1716

We will try to find a way, just documenting this...
@radl97
Copy link
Collaborator Author

radl97 commented Sep 14, 2022 •
edited
Loading

bj00rn: Seems this is still an issue in channels 2.
bj00rn: carltongibson any hope of getting https://github[.]com/django/channels/pull/1719 backported into a release of channels 2?

carltongibson: Hi bj00rn — Sorry no. We (I) don't have the bandwidth to support older versions. You're welcome to backport it yourself though.

bj00rn: Sure, I gave it a shot in https://github[.]com/django/channels/pull/1769

backport of https://github[.]com/django/channels/pull/1719 to channels 2:

carltongibson: Thanks for this. Channels 2.x isn't supported so I'll close it.

lol

@radl97
Copy link
Collaborator Author

radl97 commented Sep 14, 2022 •
edited
Loading

We applied the patch by hand in /usr/share/python3/site-packages/asgnfdmdf, it worked

@radl97 radl97 changed the title Upstream bug in 3.7.11 vs django.channels Upstream bug in 3.7.11 (3.7.14) vs django.channels Sep 14, 2022
@radl97 radl97 changed the title Upstream bug in 3.7.11 (3.7.14) vs django.channels Upstream bug in django.channels vs Python 3.7.11 (3.7.14) Sep 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@radl97