rapydscript-ns 0.8.2 → 0.8.4

package/.agignore

@@ -1 +1 @@
-lib/*
+lib/*

package/.github/workflows/ci.yml

@@ -1,38 +1,38 @@
-name: CI
-on: [push, pull_request]
-env:
-    CI: 'true'
-
-jobs:
-    test:
-        name: Test on ${{ matrix.os }} LANG ${{ matrix.lang }}
-        runs-on: ${{ matrix.os }}
-        env:
-          LANG: ${{ matrix.lang }}
-          LC_ALL: ${{ matrix.lang }}
-        strategy:
-            matrix:
-                include:
-                    - { os: ubuntu-latest, lang: en_US.UTF-8 }
-                    - { os: ubuntu-latest, lang: de_DE.UTF-8}
-                    - { os: ubuntu-latest, lang: hi_IN.UTF-8 }
-
-                    - { os: macos-latest, lang: en_US.UTF-8 }
-                    - { os: windows-latest, lang: en_US.UTF-8 }
-
-        steps:
-            - name: Checkout source code
-              uses: actions/checkout@master
-              with:
-                fetch-depth: 10
-
-            - name: Set up Node ${{ matrix.node }}
-              uses: actions/setup-node@master
-
-            - name: Install deps
-              run:
-                npm install --no-optional
-
-            - name: Test
-              run:
-                npm test
+name: CI
+on: [push, pull_request]
+env:
+    CI: 'true'
+
+jobs:
+    test:
+        name: Test on ${{ matrix.os }} LANG ${{ matrix.lang }}
+        runs-on: ${{ matrix.os }}
+        env:
+          LANG: ${{ matrix.lang }}
+          LC_ALL: ${{ matrix.lang }}
+        strategy:
+            matrix:
+                include:
+                    - { os: ubuntu-latest, lang: en_US.UTF-8 }
+                    - { os: ubuntu-latest, lang: de_DE.UTF-8}
+                    - { os: ubuntu-latest, lang: hi_IN.UTF-8 }
+
+                    - { os: macos-latest, lang: en_US.UTF-8 }
+                    - { os: windows-latest, lang: en_US.UTF-8 }
+
+        steps:
+            - name: Checkout source code
+              uses: actions/checkout@master
+              with:
+                fetch-depth: 10
+
+            - name: Set up Node ${{ matrix.node }}
+              uses: actions/setup-node@master
+
+            - name: Install deps
+              run:
+                npm install --no-optional
+
+            - name: Test
+              run:
+                npm test

package/=template.pyj

@@ -1,5 +1,5 @@
-# vim:fileencoding=utf-8
-# License: BSD Copyright: %YEAR%, %USER% <%MAIL%>
-from __python__ import hash_literals
-
-%HERE%
+# vim:fileencoding=utf-8
+# License: BSD Copyright: %YEAR%, %USER% <%MAIL%>
+from __python__ import hash_literals
+
+%HERE%

package/CHANGELOG.md

@@ -1,3 +1,42 @@
+version 0.8.4
+=======================
+  * Added support for jsx
+  * Added support for basic React components
+  * support for __new__, __getattr__, __setattr__, __delattr__, __class_getitem__, __init_subclass__
+  * added `copy` standard library
+
+
+version 0.8.0 - 0.8.3
+=======================
+
+  * Add language service with tab-completion, return type inference, hover tips, and typing exports
+  * Add source maps support for the transpiled js
+  * Add `itertools` standard library module
+  * Add `collections` standard library module
+  * Add `functools` standard library module
+  * Add `numpy` standard library module
+  * Add `async`/`await` support
+  * Add lambda expression support
+  * Add structural pattern matching (`match`/`case`) support
+  * Add starred assignment support (e.g. `a, *b = [1, 2, 3]`)
+  * Add ellipsis operator and subscript tuple support
+  * Add walrus operator (`:=`) support
+  * Add dict merge literal support (`{**a, **b}`)
+  * Add positional-only (`/`) and keyword-only (`*`) parameter separators
+  * Add `@classmethod` decorator support with improved class property access
+  * Add nested comprehension support
+  * Add overloaded operator support
+  * Add Python-style truthiness for empty lists and dicts
+  * Add `super()` support
+  * Add compiler flags to enable optional pythonic behaviors
+  * Add `any()` and `all()` builtins
+  * Add tree shaking support for reduced output size
+  * Add module mode for exporting root-level functions
+  * Add support for virtual imports
+  * Add support for bundling pythonized strings into compiled output
+  * `print` now maps to `console.log`; `window.print` maps to the JS printer dialog
+  * Add custom class mapping support in `dict()`
+
 version 0.7.22
 =======================
 

package/HACKING.md

@@ -1,103 +1,103 @@
-Hacking the RapydScript compiler
-=================================
-
-The RapydScript compiler is written in RapydScript itself and uses the
-RapydScript import system to modularize its code. The compiler source code is
-in the `src` directory. The compiled compiler is by default in the `release`
-directory. 
-
-In order to start hacking on the compiler, run the command
-
-```
-bin/rapydscript self --complete --test
-```
-
-This will generate a build of the compiler in the `dev` directory. Now, the
-rapydscript command will automatically use this build, rather than the one in
-release. If you want to go back to the release build, simply delete the `dev`
-directory.
-
-
-Code organization
--------------------
-
-The way the compiler works, given some RapydScript source code:
-
-* The source code is lexed into a stream of tokens (`src/tokenzier.pyj`)
-
-* The tokens are parsed into a Abstract Syntax Tree (`src/parse.pyj and src/ast.pyj`)
-
-* During parsing any import statement are resolved (this is different from
-  python, where imports happen at run-time, not compile time).
-
-* The Abstract Syntax Tree is transformed into the output JavaScript (`src/output/*.pyj`)
-
-* Various bits of functionality in RapydScript depend upon the *Base Library*
-  (`src/baselib*.pyj`). This includes things like the basic container types
-  (list/set/dict) string functions such as `str.format()`, etc. The baselib
-  is automatically inserted into the start of the output JavaScript.
-
-The RapydScript standard library can be found in `src/lib`. The various tools,
-such as the linter, gettext support, the REPL, etc. are in the `tools`
-directory.
-
-Tests
---------
-
-The tests are in the test directory and can be run using the command:
-```
-rapydscript test
-```
-
-You can run individual test files by providing the name of the file, as
-
-```
-rapydscript test classes
-```
-
-Modifying the compiler
--------------------------
-
-Edit the files in the `src` directory to make your changes, then use the
-`./try` script to test them.  This script will compile an updated version of
-the compiler with your changes, if any, and use it to run the snippet of code
-you pass to it.
-
-For example:
-
-```
-./try 'print("Hello world")'
-```
-
-will compile `print ("Hello world")` and show you the output on stdout. You can
-tell it to omit the baselib, so you can focus on the output, with the `-m`
-switch, like this:
-
-```
-./try -m 'print("Hello world")'
-```
-
-You can also have it not print out the JavaScript, instead directly executing the output
-JavaScript with the `-x` switch, like this
-
-```
-./try -x 'print("Hello world")'
-```
-
-If you want to test longer sections of code, you can use the `-f` switch to
-pass in the path to a RapydScript file to compile, like this:
-
-```
-./try -f myfile.pyj
-```
-
-Once you are happy with your changes, you can build the compiler and run the
-test suite, all with a single command:
-
-```
-./build
-```
-
-This will build the compiler with the updated version of itself and then run
-the test suite. If all test pass you can commit your changes and send a pull
-request :)
+Hacking the RapydScript compiler
+=================================
+
+The RapydScript compiler is written in RapydScript itself and uses the
+RapydScript import system to modularize its code. The compiler source code is
+in the `src` directory. The compiled compiler is by default in the `release`
+directory. 
+
+In order to start hacking on the compiler, run the command
+
+```
+bin/rapydscript self --complete --test
+```
+
+This will generate a build of the compiler in the `dev` directory. Now, the
+rapydscript command will automatically use this build, rather than the one in
+release. If you want to go back to the release build, simply delete the `dev`
+directory.
+
+
+Code organization
+-------------------
+
+The way the compiler works, given some RapydScript source code:
+
+* The source code is lexed into a stream of tokens (`src/tokenzier.pyj`)
+
+* The tokens are parsed into a Abstract Syntax Tree (`src/parse.pyj and src/ast.pyj`)
+
+* During parsing any import statement are resolved (this is different from
+  python, where imports happen at run-time, not compile time).
+
+* The Abstract Syntax Tree is transformed into the output JavaScript (`src/output/*.pyj`)
+
+* Various bits of functionality in RapydScript depend upon the *Base Library*
+  (`src/baselib*.pyj`). This includes things like the basic container types
+  (list/set/dict) string functions such as `str.format()`, etc. The baselib
+  is automatically inserted into the start of the output JavaScript.
+
+The RapydScript standard library can be found in `src/lib`. The various tools,
+such as the linter, gettext support, the REPL, etc. are in the `tools`
+directory.
+
+Tests
+--------
+
+The tests are in the test directory and can be run using the command:
+```
+rapydscript test
+```
+
+You can run individual test files by providing the name of the file, as
+
+```
+rapydscript test classes
+```
+
+Modifying the compiler
+-------------------------
+
+Edit the files in the `src` directory to make your changes, then use the
+`./try` script to test them.  This script will compile an updated version of
+the compiler with your changes, if any, and use it to run the snippet of code
+you pass to it.
+
+For example:
+
+```
+./try 'print("Hello world")'
+```
+
+will compile `print ("Hello world")` and show you the output on stdout. You can
+tell it to omit the baselib, so you can focus on the output, with the `-m`
+switch, like this:
+
+```
+./try -m 'print("Hello world")'
+```
+
+You can also have it not print out the JavaScript, instead directly executing the output
+JavaScript with the `-x` switch, like this
+
+```
+./try -x 'print("Hello world")'
+```
+
+If you want to test longer sections of code, you can use the `-f` switch to
+pass in the path to a RapydScript file to compile, like this:
+
+```
+./try -f myfile.pyj
+```
+
+Once you are happy with your changes, you can build the compiler and run the
+test suite, all with a single command:
+
+```
+./build
+```
+
+This will build the compiler with the updated version of itself and then run
+the test suite. If all test pass you can commit your changes and send a pull
+request :)

package/LICENSE

@@ -1,24 +1,24 @@
-Copyright (c) 2015-, Kovid Goyal <kovid@kovidgoyal.net>
-Copyright (c) 2013-2014, Alexander Tsepkov <atsepkov@pyjeon.com>
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are met:
-
-* Redistributions of source code must retain the above copyright notice, this
-  list of conditions and the following disclaimer.
-
-* Redistributions in binary form must reproduce the above copyright notice,
-  this list of conditions and the following disclaimer in the documentation
-  and/or other materials provided with the distribution.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
-AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
-FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
-SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
-CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
-OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+Copyright (c) 2015-, Kovid Goyal <kovid@kovidgoyal.net>
+Copyright (c) 2013-2014, Alexander Tsepkov <atsepkov@pyjeon.com>
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+* Redistributions of source code must retain the above copyright notice, this
+  list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice,
+  this list of conditions and the following disclaimer in the documentation
+  and/or other materials provided with the distribution.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.