Transcrypt 3.9.1__tar.gz → 3.9.3__tar.gz

transcrypt-3.9.3/.travis.yml

@@ -0,0 +1,12 @@
+addons:
+    chrome: stable
+    apt:
+        packages:
+            - chromium-chromedriver
+            
+language: python
+python:
+    - '3.9'
+    
+script:
+    - bash ./transcrypt/development/continuous_integration/run.sh

transcrypt-3.9.3/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "{}"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+  Copyright 2014, 2015, 2016, 2017 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
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   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.

transcrypt-3.9.3/MANIFEST.in

@@ -0,0 +1,14 @@
+global-include *.py *.js *.rst *.html *.css *.lyx *.pdf *.png *.gif *.jpg *.txt *.jar *.bat *
+global-exclude *.pyc .gitignore workspace.*
+
+prune .git
+prune .idea
+prune .mypy_cache
+prune build
+prune dist
+prune Transcrypt.egg-info
+prune venv
+
+prune transcrypt/development/attic
+prune transcrypt/development/docs
+prune transcrypt/development/experiments

transcrypt-3.9.3/PKG-INFO

@@ -0,0 +1,147 @@
+Metadata-Version: 2.1
+Name: Transcrypt
+Version: 3.9.3
+Summary: Python to JavaScript transpiler, supporting multiple inheritance and generating lean, highly readable code
+Home-page: https://www.transcrypt.org
+Author: Jacques de Hooge
+Author-email: info@transcrypt.org
+License: Apache 2.0
+Keywords: python,javascript,transpiler,compiler,browser,web,multiple inheritance,transcrypt,django,flask,react
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Intended Audience :: Developers
+Classifier: Natural Language :: English
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3.9
+Description-Content-Type: text/x-rst
+License-File: LICENSE
+Requires-Dist: mypy
+
+.. figure:: https://www.transcrypt.org/illustrations/ruler_banner2.png
+    :alt: Logo
+    :target: https://www.transcrypt.org
+        
+Python in the browser, precompiled for speed: https://www.transcrypt.org
+=========================================================================
+
+- Precompiled into highly readable, efficient JavaScript, downloads kB's rather than MB's
+- Multiple inheritance, optional operator overloading, metaclasses, async/await, properties, decorators, hierarchical modules etc.
+- Seamless integration with the universe of high-quality web-oriented JavaScript libraries, rather than the desktop-oriented Python ones
+- Pure Python 3.9 syntax, using Python's native parser
+- Debug directly from Python sourcecode, through integrated sourcemaps
+- Generates JavaScript for humans, resembling the Python source line by line, optionally annotated with source line numbers
+- Lightning fast JavaScript 6 code: call caching, for-loop optimization, in-line JavaScript etc.
+- Integrated static type checking and minification at the tip of a command line switch
+- Also runs on top of node.js
+- Extensive documentation with many code examples
+- Apache 2.0 license
+- Pip-install and go!
+
+Latest stable release: Berlin
+=============================
+
+`>>> GET STARTED! <https://www.transcrypt.org/#hello>`__
+========================================================
+
+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.
+
+.. figure:: https://www.transcrypt.org/illustrations/class_compare.png
+    :alt: Screenshot of Python versus JavaScript code
+    
+    **Classic OO with multiple inheritance in JavaScript**
+
+Main differences with CPython
+=============================
+
+- Web batteries: Seamless access to any existing JavaScript library 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.
+- No eval and exec of Python code. This is again part of the concept. 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
+
+    https://www.apache.org/licenses/LICENSE-2.0
+
+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 <https://github.com/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:
+
+- The automated back to back test described above, not only on Linux but also on Windows and, in case of relevant issues, on OSX.
+- Automated compilation of the manual tests, human exercising of the resulting applications and a visual check of the results.
+- Automated compilation of the demo's, human exercising of the resulting applications and a visual check of the results.
+- A documentation build, followed by a visual sample check.
+
+What's new in the latest commits
+================================
+
+- Code generator adapted to Python 3.9 parser
+- Updated README and packaging configuration
+
+Known bugs in latest commits
+============================
+
+None
+
+Other packages you might like
+=============================
+
+- Numscrypt - port of a microscopic part of NumPy to Transcrypt, using JavaScript typed arrays: https://github.com/QQuick/Numscrypt
+- SimPyLC - PLC simulator with Arduino code generation: https://github.com/QQuick/SimPyLC

transcrypt-3.9.3/README.rst

@@ -0,0 +1,127 @@
+.. figure:: https://www.transcrypt.org/illustrations/ruler_banner2.png
+    :alt: Logo
+    :target: https://www.transcrypt.org
+        
+Python in the browser, precompiled for speed: https://www.transcrypt.org
+=========================================================================
+
+- Precompiled into highly readable, efficient JavaScript, downloads kB's rather than MB's
+- Multiple inheritance, optional operator overloading, metaclasses, async/await, properties, decorators, hierarchical modules etc.
+- Seamless integration with the universe of high-quality web-oriented JavaScript libraries, rather than the desktop-oriented Python ones
+- Pure Python 3.9 syntax, using Python's native parser
+- Debug directly from Python sourcecode, through integrated sourcemaps
+- Generates JavaScript for humans, resembling the Python source line by line, optionally annotated with source line numbers
+- Lightning fast JavaScript 6 code: call caching, for-loop optimization, in-line JavaScript etc.
+- Integrated static type checking and minification at the tip of a command line switch
+- Also runs on top of node.js
+- Extensive documentation with many code examples
+- Apache 2.0 license
+- Pip-install and go!
+
+Latest stable release: Berlin
+=============================
+
+`>>> GET STARTED! <https://www.transcrypt.org/#hello>`__
+========================================================
+
+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.
+
+.. figure:: https://www.transcrypt.org/illustrations/class_compare.png
+    :alt: Screenshot of Python versus JavaScript code
+    
+    **Classic OO with multiple inheritance in JavaScript**
+
+Main differences with CPython
+=============================
+
+- Web batteries: Seamless access to any existing JavaScript library 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.
+- No eval and exec of Python code. This is again part of the concept. 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
+
+    https://www.apache.org/licenses/LICENSE-2.0
+
+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 <https://github.com/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:
+
+- The automated back to back test described above, not only on Linux but also on Windows and, in case of relevant issues, on OSX.
+- Automated compilation of the manual tests, human exercising of the resulting applications and a visual check of the results.
+- Automated compilation of the demo's, human exercising of the resulting applications and a visual check of the results.
+- A documentation build, followed by a visual sample check.
+
+What's new in the latest commits
+================================
+
+- Code generator adapted to Python 3.9 parser
+- Updated README and packaging configuration
+
+Known bugs in latest commits
+============================
+
+None
+
+Other packages you might like
+=============================
+
+- Numscrypt - port of a microscopic part of NumPy to Transcrypt, using JavaScript typed arrays: https://github.com/QQuick/Numscrypt
+- SimPyLC - PLC simulator with Arduino code generation: https://github.com/QQuick/SimPyLC