leo-editor / ast-token-tools

Abstract Syntax Tree and Token Tools

Leo https://leo-editor.github.io/leo-editor/ 6.7.8 is now available on GitHub and pypi.

Leo is an IDE, outliner and PIM.

The highlights of Leo 6.7.8

This release simplifies Leo's install process. See https://leo-editor.github.io/leo-editor/getting-started.html

• PR #3757: (leoTokens.py) Make Leo's beautifier 3x faster.
• PR #3771: Revert colorizing of f-strings.
• PR #3786: Support Nim.
• PR #3790: Add "get-unl" command to Leo's server.
• PR #3805: Fix problems with auto-completion and calltips.
• PR #3806: Fix problems with Leo's go-back and go-forward commands.
• PR #3807: Improve Leo's Python importer.
• PR #3817: Allow relative paths in gnx-based UNLs.
• The usual minor improvements and bug fixes.

Links

• Download Leo
• Install Leo
• 6.7.8 Issues
• 6.7.8 Pull Requests
• Documentation
• Tutorials
• Video tutorials
• Forum
• Download
• Leo on GitHub
• LeoVue
• What people are saying about Leo
• A web page that displays .leo files
• More links

ast-token-tools's Issues

add tests

leoAst.py with repo history has been imported, now do the same for unit tests (and then make them work of course)

determine and declare python versions

What python versions does this library and tools support?
declare in

• setup.py
• readme.md
• requirements.txt

Quickstart Hello World

For readme quickstart: a simple recipe that demonstrates the module has been installed correctly and is available for use.

Example not yet working code:

#a-last-hello.py
from ast_token_tools import leoAst as last
print(last.hello())

Out:

Hello %USERNAME%!
     -- from the AST Token & Tools library

nb: I'm using 'last' as an example because it's my personal favourite for the lib/tool's short name, but that's just a placeholder for whatever Edward decides to use officially.

investigate setuptools_scm for version management

investigate setuptools_scm for version management:
https://github.com/pypa/setuptools_scm/

I tried an earlier version of this with Leo. That didn't fit well because of some difficulties with undocumented s-scm features and Leo's a mature and multi-faceted project using a different approach. From my reading s-scm has continued to develop and might be easier to use now.

Workflow for merging leoAst and ast-token-tools 'branches'

Now and for an indeterminate length into the future, primary development of this toolkit is occuring within the arms of Leo Editor project. Presumably at some point the locus will shift to ast-token-tools. Regardless of where the activity centre is, the two need to kept in sync. This issue is about devising/capturing/documenting that workflow, and keeping it simple as possible so it's actually used.

Part 1: the initial import of leoAst.py was done using ./tools/git-copy.sh. The script creates a git patch file from one repo (e.g. leo-editor) and then applies the patch to another repo (ast-token-tools). The effect is the file or folder now exists in the destination repo with it's entire commit history intact.

I don't understand how it works, just that it does. Presumably merging in future patch sets will necessitate adapting the script or creating a new one so that subsequent 'merges' aren't duplicating history. (Or maybe git is just smart enough on it's own and we don't need to change anything!)

project name

what will the project be called? (e.g. the github name)
and what will the module be named? (e.g. import ....)

Discussion: https://groups.google.com/d/topic/leo-editor/RMpQDXfExGs/discussion

pip installable

Get to point where pip install https://github.com/leo-editor/PROJECT/archive/master.zip works.

• adapt to recommended src style dir layout
• add/adjust __init__.py as needed
• ...

leoAst - depends on Leo

leoAst.py is hardcoded to use Leo

>>> from ast_token_tools import leoAst as last
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "D:\Matt\code\ast-token-tools\ast_token_tools\leoAst.py", line 4, in <module>
    import leo.core.leoGlobals as g
ModuleNotFoundError: No module named 'leo'