Minigame is probably never going to support Python 3.

17 Responses

1. 

   1

   Stanislav Datskovskiy 
   Monday, 28 November 2016

   2.7 is not even plug-compatible with 2.6... Python per se is a crock of shit and has no permanent future in any sane scenario.

   It is exactly Perl -- a "duct tape" which is made use of simply because it makes the act of writing a sane and reusable program seem exorbitantly expensive, and the planning work involved -- seem "unnecessary". (For a complete exposition of "Perlism", refer to Naggum.)

2. 

   2

   Mircea Popescu 
   Monday, 28 November 2016

   The problem remains that you have no proper compiler of art files into C binary objects ; and the gap has to be filled with something.

   This is python, the compiler of the gaps, play on linux relies on it to get wine to interact with gnome (ie, a bunch of bash-esque confstring manipulation), minigame relies on it to get blender exports to work in crystal space (ie... very much the same, hacking chunks of data from files into a single blob) and so on and so forth.

   Until someone makes a general compiler, there will be something like python. That the various molds & assorted scum caught in the grating (ever seen Nick Coghlan's twitter stream for instance ?) imagine it relevant or important is ... well, basically what they do.

3. 

   3

   Entitled Nancy 
   Tuesday, 29 November 2016

   Down with Python 3.x!

   I'm an entitled whiner that can't handle the world changing around me! Fuck all these Johnny Come-lately's! They should keep doing things the way I'M most comfortable with!

   Because I wrapped my head around the warts of Python 2.x, I'm special! If I get hit by a bus, the world will truly lose out on that nothing valuable because millions of others also learned the warts and many of them moved on!

   Never mind I'm too much of a nancy to use a real language to begin with! I need something with a bunch of guardrails built into it! I need "features" like inheritance, cause I can't reason about problems without abstract wankery to hold my hand! I love my hand-wavey type system! I love guessing if it's one type or another I'll get and writing extra code to handle the edge cases that arise!

   -- Staticly Typed Hipster

4. 

   4

   Mircea Popescu 
   Tuesday, 29 November 2016

   If only things were so simple, you'd be adequate for the calls of the world.

5. 

   5

   Nick Coghladick 
   Tuesday, 29 November 2016

   the same design changes that improve Python 3’s Windows integration by changing several OS interfaces to operate on text rather than binary data also make it more sensitive to locale misconfiguration issues on POSIX operating systems other than Mac OS X.

   You totally got your priorities straight, dickfaces.

6. 

   6

   Mircea Popescu 
   Tuesday, 29 November 2016

   That's not the best part. The best part is when the dickface conclave admits that the whole steaming pile of crap was rushed to production before even cursory design work :

   During the pre-release design period, the lack of an immutable binary data type was identified as a problem, and the (then mutable) bytes type was renamed to bytearray and a new immutable bytes type added. The now familiar “bytes literal” syntax was introduced (prepending a “b” prefix to the string literal syntax) and the representations of the two types were also adjusted to be based on the new bytes literal syntax. With the benefit of hindsight, it has become clear another change should have been made at the same time: with so many affordances switched back to matching those of the Python 2 str type (including the use of the new bytes literal syntax to refer to that type in Python 2.6 and 2.7), bytes and bytearray should have been been switched away from behaving like a tuple of integers and list of integers (respectively) and instead modified to be containers of length 1 bytes objects, just as the str type is a container of length 1 str objects. Unfortunately, that change was not made at the time, and now backwards compatibility constraints within the Python 3 series itself makes it highly unlikely the behaviour will be changed in the future either.

   But hey, Python 4, amirite ?

   The part where Unicode is an entirely spurious piece of shit, whose mere presence literally dumbs down entire organisations whether used or not has yet to be addressed.

   Why the fuck should sandniggers & assorted orcs feed their God-forsaken chicken scribblings into a computer rather than become literate ? Computers are not for everyone.

7. 

   7

   Stanislav Datskovskiy 
   Tuesday, 29 November 2016

   Related: https://learnpythonthehardway.org/book/nopython3.html

8. 

   8

   Mircea Popescu 
   Tuesday, 29 November 2016

   The strings in Python 3 are very difficult to use for beginners. In an attempt to make their strings more "international" they turned them into difficult to use types with poor error messages. Every time you attempt to deal with characters in your programs you'll have to understand the difference between byte sequences and Unicode strings. Don't know what that is? Exactly. The Python project took a language that is very forgiving to beginners and mostly "just works" and implemented strings that require you to constantly know what type of string they are. Worst of all, when you get an error with strings (which is very often) you get an error message that doesn't tell you what variable names you need to fix.

   Imagine if you will, I'm supposed to have artists delve into haskellian arcana ? Jaysus.

9. 

   9

   walter 
   Monday, 5 December 2016

   I found http://lucumr.pocoo.org/2014/5/12/everything-about-unicode/ much better than the 'learnpythonthehardway' link. It talks technical facts and shows with code how bad the situation is.

10. 

    10

    Mircea Popescu 
    Tuesday, 6 December 2016

    Not a bad read.

11. 

    11

    Cristian 
    Tuesday, 5 September 2017

    The devlog link is basically broken.

12. 

    12

    Cristian 
    Wednesday, 6 September 2017

    Python was designed for noobs from the start, so it's not a bug, it's a feature.

    That being said, Java, C#, JavaScript and TCL have Unicode strings. Even Go and Rust have some built-in support.

    Are old polimedia.us/trilema URLs still working? Talkin' about API breakage...

1. 13

   Notes on Computer Graphics - Transfer vs. Display « Ossa Sepia (via Pingback)
   Saturday, 4 January 2020

   [...] ways in which people are morons, from the pure bobeckistan of blender (and let's not forget how python got indexed in the first place) to a very thick stripperweb-style tarabostes idiocy. mircea_popescu: do you [...]

2. 14

   Romania's a dumb slut! Long live Pharmacy! My fuckstick! on Trilema - A blog by Mircea Popescu. (via Pingback)
   Wednesday, 8 January 2020

   [...] deploys with a master's hand the Romanian tradition of мат, partly because English is a sort of Python 3 these days (in the sense of having entirely lost any sort of contact with any kind of lived life, [...]

3. 15

   The TMSR-OS implicit clients on Trilema - A blog by Mircea Popescu. (via Pingback)
   Wednesday, 8 January 2020

   [...] python fucking sucks in and of itself, on its own merits ; but also because its community is toxically idiotic beyond any known measure, perhaps outside of wikipedia). This is a large hunk, granted, but it is [...]

4. 16

   Notes on Computer Graphics: Formats, Exporters and Blendering « Ossa Sepia (via Pingback)
   Friday, 18 December 2020

   [...] where one cares to look, from a weird sort of anti-management at the top to a full embrace of Python's own wrong choices, ant-like overspecialisation and overfitting of artists and the resulting impossibility of any [...]

5. 17

   A Gentoo install on JWRD desktop « Dorion Mode (via Pingback)
   Friday, 25 December 2020

   [...] is married to Python, which is a clear mark against. Nevertheless, if we're stuck with Python, Python2 it'll be. eselect python list eslect python set [...]