New Research: Supply Chain Attack on Axios Pulls Malicious Dependency from npm.Details → →
Socket
Book a DemoSign in
Socket
Book a DemoSign in

devshell

Package Overview
Dependencies
Maintainers
1
Versions
7
Alerts
File Explorer

Advanced tools

License
Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

devshell - pypi Package Compare versions

Comparing version
0.0.4
 to
0.0.5
src/__init__.py
src/__pycache__/__init__.cpython-38.pyc

Sorry, the diff of this file is not supported yet

+1
-1
docs/devshell/index.html

@@ -29,3 +29,3 @@ <!doctype html>

</summary>
<pre><code class="python">__version__ = &#39;0.0.4&#39;
<pre><code class="python">__version__ = &#39;0.0.5&#39;
from .injector import doctestify, set_end_interactive

@@ -32,0 +32,0 @@ from .shell import DevshellCmd</code></pre>

+10
-10
PKG-INFO
Metadata-Version: 2.1
Name: devshell
Version: 0.0.4
Version: 0.0.5
Summary: Shell-like tool to make it easier to develop python code

@@ -85,13 +85,13 @@ Home-page: https://github.com/mmiguel6288code/devshell

## Doctests
If you navigate to a code block, you can examine the docstring and function definition using the ```bash doc ``` command.
You can run any doctests present in that code block by using the ```bash doctest ``` command.
You can call ```bash doctestify ``` to enter into an interactive session with the module's contents imported. All input and output in this session is recorded, and when the session is closed via CTRL+D, the input/output is appended to the docstring of the current code block as an additional set of doctests.
If you navigate to a code block, you can examine the docstring and function definition using the ```doc ``` command.
You can run any doctests present in that code block by using the ```doctest ``` command.
You can call ```doctestify ``` to enter into an interactive session with the module's contents imported. All input and output in this session is recorded, and when the session is closed via CTRL+D, the input/output is appended to the docstring of the current code block as an additional set of doctests.
```bash doctestify resume ``` will open the interactive session and execute all existing doctest commands in the current docstring before turning interactive control over to you. This is useful if you are tweaking code while repeatedly running some test. You don't have to rewrite any setup code multiple times, just use what is in the docstring.
```doctestify resume ``` will open the interactive session and execute all existing doctest commands in the current docstring before turning interactive control over to you. This is useful if you are tweaking code while repeatedly running some test. You don't have to rewrite any setup code multiple times, just use what is in the docstring.
## Pytest/Coverage
```bash pytest``` and ```bash coverage``` - pretty self-explanatory. Coverage runs pytest and doctests and produces a combined report.
```pytest``` and ```coverage``` - pretty self-explanatory. Coverage runs pytest and doctests and produces a combined report.
## Debugging
```bash debug(5,10)``` takes the current function or class and calls it with those arguments, entering debug mode on the first line.
```debug(5,10)``` takes the current function or class and calls it with those arguments, entering debug mode on the first line.
If the current code block is a module or package, it will ens

@@ -101,7 +101,7 @@

## Looking at code
```bash grep pattern [OPTIONS]``` runs a grep-like function that is filtered on the current code block.
```grep pattern [OPTIONS]``` runs a grep-like function that is filtered on the current code block.
```bash editvim``` opens vim to the line corresponding to the currently targeted code block.
```editvim``` opens vim to the line corresponding to the currently targeted code block.
```bash source``` opens a paginated view with the text of the current code block
```source``` opens a paginated view with the text of the current code block

@@ -108,0 +108,0 @@ 

+9
-9
README.md

@@ -75,13 +75,13 @@ # devshell

## Doctests
If you navigate to a code block, you can examine the docstring and function definition using the ```bash doc ``` command.
You can run any doctests present in that code block by using the ```bash doctest ``` command.
You can call ```bash doctestify ``` to enter into an interactive session with the module's contents imported. All input and output in this session is recorded, and when the session is closed via CTRL+D, the input/output is appended to the docstring of the current code block as an additional set of doctests.
If you navigate to a code block, you can examine the docstring and function definition using the ```doc ``` command.
You can run any doctests present in that code block by using the ```doctest ``` command.
You can call ```doctestify ``` to enter into an interactive session with the module's contents imported. All input and output in this session is recorded, and when the session is closed via CTRL+D, the input/output is appended to the docstring of the current code block as an additional set of doctests.
```bash doctestify resume ``` will open the interactive session and execute all existing doctest commands in the current docstring before turning interactive control over to you. This is useful if you are tweaking code while repeatedly running some test. You don't have to rewrite any setup code multiple times, just use what is in the docstring.
```doctestify resume ``` will open the interactive session and execute all existing doctest commands in the current docstring before turning interactive control over to you. This is useful if you are tweaking code while repeatedly running some test. You don't have to rewrite any setup code multiple times, just use what is in the docstring.
## Pytest/Coverage
```bash pytest``` and ```bash coverage``` - pretty self-explanatory. Coverage runs pytest and doctests and produces a combined report.
```pytest``` and ```coverage``` - pretty self-explanatory. Coverage runs pytest and doctests and produces a combined report.
## Debugging
```bash debug(5,10)``` takes the current function or class and calls it with those arguments, entering debug mode on the first line.
```debug(5,10)``` takes the current function or class and calls it with those arguments, entering debug mode on the first line.
If the current code block is a module or package, it will ens

@@ -91,7 +91,7 @@

## Looking at code
```bash grep pattern [OPTIONS]``` runs a grep-like function that is filtered on the current code block.
```grep pattern [OPTIONS]``` runs a grep-like function that is filtered on the current code block.
```bash editvim``` opens vim to the line corresponding to the currently targeted code block.
```editvim``` opens vim to the line corresponding to the currently targeted code block.
```bash source``` opens a paginated view with the text of the current code block
```source``` opens a paginated view with the text of the current code block
+10
-10
src/devshell.egg-info/PKG-INFO
Metadata-Version: 2.1
Name: devshell
Version: 0.0.4
Version: 0.0.5
Summary: Shell-like tool to make it easier to develop python code

@@ -85,13 +85,13 @@ Home-page: https://github.com/mmiguel6288code/devshell

## Doctests
If you navigate to a code block, you can examine the docstring and function definition using the ```bash doc ``` command.
You can run any doctests present in that code block by using the ```bash doctest ``` command.
You can call ```bash doctestify ``` to enter into an interactive session with the module's contents imported. All input and output in this session is recorded, and when the session is closed via CTRL+D, the input/output is appended to the docstring of the current code block as an additional set of doctests.
If you navigate to a code block, you can examine the docstring and function definition using the ```doc ``` command.
You can run any doctests present in that code block by using the ```doctest ``` command.
You can call ```doctestify ``` to enter into an interactive session with the module's contents imported. All input and output in this session is recorded, and when the session is closed via CTRL+D, the input/output is appended to the docstring of the current code block as an additional set of doctests.
```bash doctestify resume ``` will open the interactive session and execute all existing doctest commands in the current docstring before turning interactive control over to you. This is useful if you are tweaking code while repeatedly running some test. You don't have to rewrite any setup code multiple times, just use what is in the docstring.
```doctestify resume ``` will open the interactive session and execute all existing doctest commands in the current docstring before turning interactive control over to you. This is useful if you are tweaking code while repeatedly running some test. You don't have to rewrite any setup code multiple times, just use what is in the docstring.
## Pytest/Coverage
```bash pytest``` and ```bash coverage``` - pretty self-explanatory. Coverage runs pytest and doctests and produces a combined report.
```pytest``` and ```coverage``` - pretty self-explanatory. Coverage runs pytest and doctests and produces a combined report.
## Debugging
```bash debug(5,10)``` takes the current function or class and calls it with those arguments, entering debug mode on the first line.
```debug(5,10)``` takes the current function or class and calls it with those arguments, entering debug mode on the first line.
If the current code block is a module or package, it will ens

@@ -101,7 +101,7 @@

## Looking at code
```bash grep pattern [OPTIONS]``` runs a grep-like function that is filtered on the current code block.
```grep pattern [OPTIONS]``` runs a grep-like function that is filtered on the current code block.
```bash editvim``` opens vim to the line corresponding to the currently targeted code block.
```editvim``` opens vim to the line corresponding to the currently targeted code block.
```bash source``` opens a paginated view with the text of the current code block
```source``` opens a paginated view with the text of the current code block

@@ -108,0 +108,0 @@ 

+2
-0
src/devshell.egg-info/SOURCES.txt

@@ -10,2 +10,4 @@ LICENSE

docs/devshell/shell.html
src/__init__.py
src/__pycache__/__init__.cpython-38.pyc
src/devshell/__init__.py

@@ -12,0 +14,0 @@ src/devshell/__main__.py

+1
-1
src/devshell/__init__.py

@@ -1,4 +0,4 @@

__version__ = '0.0.4'
__version__ = '0.0.5'
from .injector import doctestify, set_end_interactive
from .shell import DevshellCmd
src/devshell/__pycache__/__init__.cpython-38.pyc

Sorry, the diff of this file is not supported yet