Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Make `tools/configure.py` work with Python 3.x
See original GitHub issueCurrently tools/configure.py fails with an error when run with Python 3. It makes things complicated when your build system already uses other scripts done in Python 3. In the perfect scenario both flavors, Py2 and Py3, would be supported.
Issue Analytics
- State:
- Created 6 years ago
- Comments:23 (17 by maintainers)
Top Results From Across the Web
Python 3 Upgrade Guide — Deadline 10.1.23.6 documentation
This guide is for users that have made custom Python workflows or have modified any Python scripts shipped with Deadline. If you aren't...
Read more >Changing PyScripter to work with different Python Versions
I'm using PyScripter for writing python programs and I can't figure out how to make it work with Python26 on my computer.
Read more >Configuring Duktape 2.x for build
The configure.py tool subsumes genconfig.py : it generates both a duk_config.h and prepared sources matching the configuration. This makes it possible to modify ......
Read more >4. Module Authoring - OpenDSA System Documentation
To create a “book”, you must invoke OpenDSA/tools/configure.py , being sure to ... Most exercises and visualizations are embedded into the module from ......
Read more >3. Compiling Book Instances: OpenDSA Configuration
A book instance is made of of “modules”, where each module is a single ReStructuredText file. ... python tools/configure.py config/foo.json --no-lms.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think moving to JS makes most sense, and I actually already have most of the tooling already rewritten in JS. It’s waiting to be merged when I get a chance to work on it for a few days 😃
The JS tooling works on Node.js but also on Duktape itself (not just in theory but in practice too 😃, making it possible to run the tooling on any target supporting Duktape. To run the tooling on Duktape one needs to bootstrap Duktape with a few additional native bindings (like a wrapper for system(), access to command line arguments, etc).
It’s Node.js based now, in https://github.com/svaarala/duktape/tree/master/src-tools. It will eventually be self-hostable with Duktape too.