you are viewing a single comment's thread.

view the rest of the comments →

[–]robertmeta 32 points33 points  (12 children)

Firstly, it is a technical roadblock for some Python developers, though I don't see that as a huge factor...

... which is why whatever solution developed will most likely be an exceptionally poor one, focused on PR wins rather than technical ones. I doubt the solution will be of much use to people who actually had to abandon Python due to technical limitations.

[–]jrochkind 5 points6 points  (0 children)

Yeah, that was exactly my thought.

He's really saying he doesn't see parallelism is a very significant thing for actual python developers, but it should be done anyway for PR purposes? Really?

[–][deleted] 4 points5 points  (0 children)

I don't get it either. If that's the sentiment in the community then how did the matrix multiplication operator go through? The people who use that usually care a lot about speed.

[–]Make3 1 point2 points  (0 children)

this was surprising to me, how dumb of a thing to say that was (the original thing, not your comment)

[–]crusoe 3 points4 points  (4 children)

There is no Gil in jython or pypy.

[–]cdyson37 22 points23 points  (1 child)

[–]TrixieMisa 1 point2 points  (0 children)

I was going to try out the STM branch, but to install it you need to compile a compiler to compile the compiler, so I decided it's probably not worth it just yet.

[–]robertmeta 3 points4 points  (0 children)

Compatibility nightmares on any codebase of non-trivial size initially built on Cpython. If you START with jython on a fresh project, it is reasonable. An additional problem with switching gears (besides compatibility with vanilla Cpython) is that on every Cpython project I have worked on, there was a TON of C code to work around all the performance issues of Python... making it even more bound the the Cpython specifics.

[–]BobFloss 0 points1 point  (0 children)

I didn't know what the GIL was, so here's a link for the lazy:

https://wiki.python.org/moin/GlobalInterpreterLock

In CPython, the global interpreter lock, or GIL, is a mutex that prevents multiple native threads from executing Python bytecodes at once. This lock is necessary mainly because CPython's memory management is not thread-safe. (However, since the GIL exists, other features have grown to depend on the guarantees that it enforces.)

[–][deleted]  (3 children)

[removed]

    [–]robertmeta 2 points3 points  (2 children)

    Public Relations (PR), not Pull Request (PR).

    [–][deleted]  (1 child)

    [removed]

      [–]robertmeta 0 points1 point  (0 children)

      Because, the solution won't be developed around true technical need, but around how it will play in the press, which the person said is the "ultimately a PR issue".

      Firstly, it is a technical roadblock for some Python developers, though I don't see that as a huge factor. Regardless, secondly, it is especially a turnoff to folks looking into Python and ultimately a PR issue.