Frankly, I think pythonium approach is superior to every other solutions. Anything other solution does, Pythonium can do, except it's faster.What can prevent you from contributing to such a projects? Mind the fact, that I'm willing to change the license to a more liberal license (LGPLv3) if people come and contribute to the project.What do you think about merging Python in the browser effort into one unique project?Héllo,Pythonium [0] creator here. I write this email to ask the community what they think about merging the different efforts to have Python in the browser.
If you don't know Pythonium, basicly current version use Python 3 ast parser to generate, fast javascript code unlike Brython and Skulpt and like pyjaco, pyjs pyjeon which is written in javascript. Unlike Brython and Skulpt which are self hosted.
Like I said, it can be self-hosted, but with proper tooling [1] we don't need that.
Also, I don't care about the name and we can take whatever name the community think is best.So what's do you think?Make sure to have pythonium-users@googlegroups.com in the reponse header, so that other people can follow the conversation.
Best regards,
Amirouche
[0] https://github.com/pythonium/pythonium
[1] Integration with frameworks, compile server with inotify, backend side compilation
Could you change it to apache license? That is what pyjs uses.
I could not find the Pythonium Veloce source mentioned in the readme, that seems closest to the problem that pyjs is trying to solve.
--
---
You received this message because you are subscribed to the Google Groups "Pyjs.org Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pyjs-users+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Could you change it to apache license? That is what pyjs uses.
I could not find the Pythonium Veloce source mentioned in the readme, that seems closest to the problem that pyjs is trying to solve.
Hi Amirouche,Can you provide some more details on what you see being merged?
If you are asking whether you can become a contributor on pyjs then I would say of course!
I reviewed some of the Pythonium Core code and I'm not sure if any of that would be worth merging with pyjs. It seems like very preliminary experimental implementation.
The difference between pyjs and literally every other Python to JavaScript implementation out there is that pyjs actually supports 95% of Python semantics... including multiple inheritance, etc.
Personally, unless the eventual goal is 100% Python support I don't see any point in these semantic-free translators.
If you just want an alternative to writing JS syntax I would highly recommend CoffeeScript. And if you want to re-use code between CPython and a web browser than you can't really avoid implementing as much of Python semantics as possible. Pyjs gets enough of the semantics implemented to be productive but once you start trying to build frameworks or more complex code the remaining 5% of missing semantics really gets in the way. That's where we need the most help and effort.
2013/11/20 Lex Berezhny <l...@damoti.com>Hi Amirouche,Can you provide some more details on what you see being merged?We could share demos, compatibility test suite, documentation, etc...
If you are asking whether you can become a contributor on pyjs then I would say of course!The thing is in Pythonium we get the extra feature that the three flavors of the compiler (Core, Veloce & Compliant) will be somewhat compatible so that people can downgrade easly from one version to another. This is the extra feature I really like, since it allows to create in pure Python and then have the extra flexibility to optimise critical paths.
I reviewed some of the Pythonium Core code and I'm not sure if any of that would be worth merging with pyjs. It seems like very preliminary experimental implementation.Actually it's the 4th complete rewrite I do. Pythonium Core flavor, the only code available yet, only aims at supporting JavaScript semantic with a Python syntax.
The difference between pyjs and literally every other Python to JavaScript implementation out there is that pyjs actually supports 95% of Python semantics... including multiple inheritance, etc.Personally, unless the eventual goal is 100% Python support I don't see any point in these semantic-free translators.It is aiming 100% support.
If you just want an alternative to writing JS syntax I would highly recommend CoffeeScript. And if you want to re-use code between CPython and a web browser than you can't really avoid implementing as much of Python semantics as possible. Pyjs gets enough of the semantics implemented to be productive but once you start trying to build frameworks or more complex code the remaining 5% of missing semantics really gets in the way. That's where we need the most help and effort.Thanks for pointing me in the right direction.
If you decide to continue with your separate project I can see two different paths of collaboration for Pythonium and Pyjs:1. test suite as discussed earlier2. a runtime engine, you call this "pythonium.veloce.js" in your readmeI think both of those could be independent projects that both Pyjs and Pythonium could depend on and thus allow some diversity and at the same time some re-use of resources on the really hard stuff.