source code?

[rzeta0]

Is the source code not visible on GitHub?

[nvllsvm]

The readme indicates that v2 is currently closed source.

I have no clue why this is. Can someone shed some light here?

[nvllsvm]

Found the answer in the Pyston blog post from October 26, 2020:

Our plan is to open-source the code in the future, but since compiler projects are expensive and we no longer have benevolent corporate sponsorship, it is currently closed-source while we iron out our business model.

Very disappointing, though understandable.

[shayneoneill]

The combination of a non "ironed out [..] business model" and closed source is bit of a warning sign, if you ask me. I just cant figure out how I'd justify rolling out Pyston in workplace projects if its a closed source product with a dependency on a non solvent commercial entity. No offence, its just.... not promising if theres no obvious escape route if the onderlying company hemorages out from a lack of capital or income. I mean.. get that sorted out, and its a different story, but until then, closed source startups push risk onto the end user, and thats not safe to bet on.

[Correct-Syntax]

This should be open-source, period.

[machineko]

This should be open-source, period.

Not sure I think its fair to get paid for your work 😄
But if u like to work for free i can give u some of my tasks 📦

[Correct-Syntax]

Not sure I think its fair to get paid for your work

Of course it's fair, but for something like this to go closed-source (especially since it was open-source), is pretty disappointing.

But if u like to work for free i can give u some of my tasks

Well, I'm already too busy working "for free", ironically (in more ways than you can imagine). 😄 I already do a lot of open-source stuff myself as well.

At the same time, I can see that this project would need a lot of resources...it's just a shame. It could get a lot more support from the Python community if it was OS -that's for sure. -I have yet to find anyone that doesn't want Python to be faster.

[yanghao]

pyston v2 is awesome ... I just ran my RISCV python simulator it is twice as fast as cpython (pypy3 is not yet reaching 3.8 so I cannot test yet ...).

I think it is fair for anyone to decide if their code goes open source or closed source, I would love to see it open sourced but I fully understand everyone has bills to pay.

In my personal opinion, people who use python is not using it for execution speed ... the focus is mainly on development speed. And when we surely need execution speed I'd re-write the hot-path as a C-extension (or even spin-off in golang ... for example). So if pyston really wants a bigger audience I think it should try not to be just a cpython clone ... but rather with something new/more.

One of the features I and a few others really missed is the possibility to overload the assignment operation "=". You see, in python you can almost overload all other mathematical operations, but not assignment, not the new assignment expression (:=). By given users the capability to overload this two operators like the __add__() and __sub__(), you immediately getting rid of the whole descriptor thing and having a much better alternative, like now you can just create descriptor-like object dynamically directly from your __init__() call and don't need meta-programming anymore for that purpose (nor abusing __getattribute__()). Second, a lot of beautify domain specific language can be designed by assign new meanings for assignment ... and much much more.

Had a very loooooooong discussion on the python-dev mailing list about this feature some time ago, no-body was able to give any valid technical objections but it was essentially rejected as only a few (compared to the huge python army ...) are interested (of course only a few are trying to do DSL design in python ... majority went for scala ...).

This could really set pyston apart from cpython.

[shayneoneill]

Not sure I think its fair to get paid for your work 😄
But if u like to work for free i can give u some of my tasks 📦

Nobody said anything about not getting paid for work. After all, many of the largest companies in tech do open source.

The problem with this is, its too dangerous commercially to risk adding a project dependency thats closed source from a company with unclear financial stability. If it was open source, that would not be a problem, and would provide a strong opportunity for the company behind Pyston to sell support and other services.