Skip to content

Make the book less (or more) editor-specific. Also, conciseness. #35

@mnmelo

Description

@mnmelo

I started teaching this year using JupyterLab and notebooks. The book assumes a non-interactive scripting interface, which is ok, but there are some mentions to IDE-specifics. I just committed a change (0df3f3f) where I removed a reference to PyScripter behavior.

OTOH, I felt the need to, in the same commit, hint at a Jupyter notebook shortcut. I realize I should have posted a PR. If you disagree, please just roll back that commit.

And while I think it is wise to cover more (modern) cases, the book is already quite thick as it is. An option would be to use click-to-reveal boxes for this sort of comments:

Jupyter

If you are using JupyterLab you are part of the enlightened future (and should press Shift+Tab to access online function documentation).

"But I heard Tcl is a nice language"

Cursed shall be the fruit of your womb and the fruit of your ground, the increase of your herds and the young of your flock.

Come to think of it, a great deal of notes, remarks, and even whole paragraphs could be relegated to such click-to-reveal boxes, perhaps making chapter 3 easier to digest.

What do you guys think?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions