Python 2.7 is dead. No "if"s, no "but"s, no "we're keeping it around because...": it's well and truly dead,

Given that it got killed on January first, 2020, which is nearing two months ago, can we remove it from the README.md as a valid requirement? (as well as everywhere else it's still being referenced?)

On a weekly basis, customer report issues around the 15 second timeout. This problem manifests as Exceptions and looks like a timeout.

We need to offer a more robust guidenance around Async / Long-Running operations. This guidenance likley takes the form of:

1. Your bot responds very quickly.
2. Do Needed Processing()
3. Send the result to the user as a Async / Proactive message.

There

if I understood it corretly from README.MD, we can install like this:

$ git clone https://github.com/donnemartin/dev-setup.git && cd dev-setup
$ ./.dots bootstrap osxprep brew osx

and later when we need datastores, we run

$ cd ~/dev-setup
$ ./.dots datastores

I understand that bootstrap copies the dot files to the home directory, such as .bash_profile and .exports.
but

I was wondering, should we include a call to action when an error boundary is triggered asking our users to report the issue to us via Github?

Something like:

An unhandled error occurred in the application. We apologize for the inconvenience! You can notify the development team by opening an issue on our Github repository. Thank you for us

Short Summary

The page of the command id references is broken, used to work on the old docs:

http://docs.komodoide.com/SDK/commandid

Was looking for this issue on the forum:

https://community.komodoide.com/t/userscript-to-make-sure-editor-tab-gets-swtiched-on-ctrl-tab/4833

Suppose someone add a new global package and modify the requirements file.
It would be nice if nodeenv had an option to read again the requirements file and reinstall missing dependencies, instead to say Environment already exists

I've been looking at the repo structure and would like to make the core repo more approachable. I've been procrastinating on finishing #91 due to travel, #142 will target the README and #152 is in, so here are a few ideas:

• Finish #91, agree on #142
• Keep only core docs (CONTRIBUTING.md, a single INSTALL.md) in the main repo
• Move detailed documentation to the website's repo (this is the

Instructions aren't sufficient to deploy as it misses a lot of steps. Actual deployment instructions are mostly the same as https://cloud.google.com/python/django/appengine

!pip install pixiedust
!pip install pixiedust_node

import pixiedust_node

%%node
var date = new Date();
print(date);

TypeError                                 Traceback (most recent call last)
<ipython-input-4-26ef6f3fb6e5> in <module>()
----> 1 get_ipython().run_cell_magic('n

Write a class method recursivePrint(int count) of a class Recursion which prints "z y x w "
on the first line, "z y x " on the second line, ..., "z " on the fourth line by recursion if count is 4. If
count is n (n <= 26), n lines should be printed and the first line contains "z y x ...? ", where "?" is the
nth letter starting from "z". Note that there is a space after each letter.
Test it usin

DFile Alias or Commands

zch shell https://ohmyz.sh/

dfile() {
    if [ $# -eq 0 ]; then
        echo -e "No arguments specified. Usage: echo dfile /tmp/test.md cat /tmp/test.md | dfile test.md";
        return 1;
    fi; 
    tmpfile=$( mktemp -t transferXXX ); 
    if tty -s; then 
        basefile=$(basename "$1" | sed -e 's/[^a-zA-Z0-9._-]/-/g'); 
        curl --progress-bar