4 ms·

Why Django 2.2? That version is no longer supported, and I'm guessing there's some technical reason you are using the obsolete version? (Production Django is no

Why Django 2.2? That version is no longer supported, and I'm guessing there's some technical reason you are using the obsolete version? (Production Django is now on major version 4)

ingenieroariel 4y ago
The technical reason for choosing Python 3.6 no longer applies due to how quickly cosmo has advanced in the past months (in particular thread support). jart and ahgamut were the ones who made it happen, I am only a python.com user. But if you want Django 4 and Python 3.11, here is some info copied from the website: 3. Newer Python and newer Django? It is possible to have a djngo.com with Django 4 and Python 3.11. Solved by aghgamut who was the first to port Python to Cosmopolitan. Please note that this Python and the one that djngo.com use are different, the later has been heavily optimized by jart to run well on cosmo, the former is as close as upstream as you can get. Choose your destiny. curl -O https://djngo.com/djngo4-py311.com https://djngo.com/djngo4-py311.com
jart 4y ago
The cosmo monorepo currently vendors Python 3.6, since cosmo originally didn't have threads support and that was the last version before threads became mandatory. I'm pretty happy with the old version since I've been using Django since the 2000's. I put a lot of work into enhancing monorepo cosmo python with things like a better REPL that works across platforms. It may not be supported by the Python team, but it's supported by me. However the future will probably be building Python w/ Cosmo outside the monorepo. See the other comments for details on how to use APE + Python 3.11 for a modern experience.
ahgamut 4y ago
https://github.com/ahgamut/cpython/tree/cosmo-djngo https://github.com/ahgamut/cpython/tree/cosmo-djngo Python 3.11.0rc1, Django 4.1.7. I think ingenieroariel also has a binary available on the website. It's a proof-of-concept (because I wrote it just a few hours back), but it shows that we could have the latest version of Python+Django packaged in a single-file executable. Someone could definitely improve upon the build process (like it was done for Python3.6) and add more packages if they wanted.

Why Django 2.2? That version is no longer supported, and I'm guessing there's some technical reason you are using the obsolete version? (Production Django is now on major version 4)

ingenieroariel 4y ago

The technical reason for choosing Python 3.6 no longer applies due to how quickly cosmo has advanced in the past months (in particular thread support). jart and ahgamut were the ones who made it happen, I am only a python.com user. But if you want Django 4 and Python 3.11, here is some info copied from the website: 3. Newer Python and newer Django? It is possible to have a djngo.com with Django 4 and Python 3.11. Solved by aghgamut who was the first to port Python to Cosmopolitan. Please note that this Python and the one that djngo.com use are different, the later has been heavily optimized by jart to run well on cosmo, the former is as close as upstream as you can get. Choose your destiny. curl -O https://djngo.com/djngo4-py311.com https://djngo.com/djngo4-py311.com

jart 4y ago

The cosmo monorepo currently vendors Python 3.6, since cosmo originally didn't have threads support and that was the last version before threads became mandatory. I'm pretty happy with the old version since I've been using Django since the 2000's. I put a lot of work into enhancing monorepo cosmo python with things like a better REPL that works across platforms. It may not be supported by the Python team, but it's supported by me. However the future will probably be building Python w/ Cosmo outside the monorepo. See the other comments for details on how to use APE + Python 3.11 for a modern experience.

ahgamut 4y ago

https://github.com/ahgamut/cpython/tree/cosmo-djngo https://github.com/ahgamut/cpython/tree/cosmo-djngo Python 3.11.0rc1, Django 4.1.7. I think ingenieroariel also has a binary available on the website. It's a proof-of-concept (because I wrote it just a few hours back), but it shows that we could have the latest version of Python+Django packaged in a single-file executable. Someone could definitely improve upon the build process (like it was done for Python3.6) and add more packages if they wanted.