Transcrypt #42
metaperl
started this conversation in
Framework Discussion: Specific
Transcrypt
#42
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Python in the browser, precompiled for speed: https://www.transcrypt.org
kB's rather than MB's
async/await, properties, decorators, hierarchical modules etc.
JavaScript libraries, rather than the desktop-oriented Python ones
by line, optionally annotated with source line numbers
optimization, in-line JavaScript etc.
command line switch
Latest stable release: Berlin
>>> GET STARTED!
Thanks to everyone who contributed!
Readability
As can be seen below, there's a simple parallel between the Python and
the JavaScript code. In combination with the use of sourcemaps, this
enables efficient debugging. Also, code can be tested from the command
prompt using stubs.
Main differences with CPython
has been favored over inclusion of many Python libraries in the
distribution. There are some exceptions to this rule, e.g. math,
cmath, random, itertools, re, time, datetime and turtle, and some
more may follow, but in general the accent is on libraries that are
relevant in the browser.
Transcrypt code is compiled, optimized and minified in advance to
warant fast page loads. In this respect its design goal is
fundamentally different from tools that compile on the fly in the
browser. Transcrypt is targeted towards building professional,
extensive, real world web applications that load and run as fast as
their JavaScript counterparts, but offers Pythonically clean,
modular structure and maintainability.
License
Copyright 2014 - 2023 Jacques de Hooge, GEATEC engineering,
www.geatec.com
Licensed under the Apache License, Version 2.0 (the "License"); you
may not use this file except in compliance with the License. You may
obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
How to contribute
Transcrypt started out as a personal repo, owned by Jacques de Hooge. As
the project caught on and the number of people contributing issues,
ideas and code grew, the repo was transferred to the QQuick
organisation, to be able to form a developer team on GitHub. Then more
recently, to insure its continued development, the GitHub repo has been
moved to TranscryptOrg, where
Transcrypt and related projects can be more centrally located.
There was also a clear message in this: Transcrypt isn't owned by
anyone in particular. It is the collective property of everyone using it
or contributing to it. At the same time the need was felt to keep a very
firm grip on code quality, especially of the core.
Everything under ../transcrypt/modules/org/transcrypt plus the file
../transcrypt/__main__.py is considered to be part of Transcrypt's
core. A major design goal is to keep the core small and fast. This means
that some CPython facilities were deliberately left out or simplified.
Core development is still mainly done by Jacques, but with the input of
many great ideas submitted as issues. If you want to improve something
in the core, this is best initiated by first opening an issue for it.
Opening a pull request directly can lead to disappointment, although all
effort is made to take good ideas seriously.
All other parts of Transcrypt are referred to as periphery. While a good
quality pull request for the periphery stands a reasonable chance of
being accepted, still it is wise to start an issue beforehand, allowing
coordination and preventing waste of effort.
A special place is taken by implementing standard libraries. While
Transcrypt mostly relies on browser-centric JavaScript libraries,
availability of a limited number of standard libraries will help
acceptance by Python programmers. So you're most welcome to make a
contribution here. The design goal again is: better 90% complete, fast,
small, and reliable, than 100% complete, slow, bulky and buggy. If you
contribute a library, please also contribute an autotest (see docs) and
some documentation for it. The supported platforms are Windows and Linux
(and, with that, OSX).
While being open and respectful to any good ideas, the final say as to
what gets in and what doesn't, is with Jacques. So this is a
dictatorial rather than a democratic project. Being a sailer himself,
Jacques values the notion of having one captain on a ship. The captain
doesn't own the ship, but he serves the passengers by consulting with
the crew and plotting one stable course.
Another possibility to contribute libraries to Transcrypt is by
submitting them as separate packages to PyPi. In that case be sure to
add the keyword Transcrypt to allow people to find your package. Making
your package pip-installable will also help it to catch on. Contributing
packages via PyPi of course means total freedom for the developer.
Deployment testing
The full set of testlets is described in the documentation and comes
with the distribution. Each release is preceded by at least the
following tests:
but also on Windows and, in case of relevant issues, on OSX.
resulting applications and a visual check of the results.
resulting applications and a visual check of the results.
What's new in the latest commits
Known bugs in latest commits
None
Other packages you might like
JavaScript typed arrays: https://github.com/QQuick/Numscrypt
https://github.com/QQuick/SimPyLC
Beta Was this translation helpful? Give feedback.
All reactions