Skip to main content

INCOR

INstant COde Runner runs the programs present in the mentioned directory instantaneously as and when changes are saved.

Version

Quality

Documentation

PyPI version

Code Health

Documentation Status

Requirements

  • python>=2.7

  • watchdog>=0.8.2

  • psutil>=4.3.0

Getting Started

Install it using pip

sudo pip install incor

Or

Clone this repository to get started.

git clone https://github.com/lakshmanaram/Incor.git

And install it.

python setup.py install

You can also install it for development.

python setup.py develop

How to Use

Nagigate to the folder where you want the files to be compiled and executed instantly and type this in the terminal

incor

Or else you can run it directly with the path of the directory.

incor /path/to/the/directory

General template for running incor.

incor /optional/path/to/the/directory [<option> <value> ...]

Using Templates

You can also add some template files in the directory where incor runs. The template files should be of the form ‘template.(some_extension)’ for example ‘template.c’ or ‘template.py’. Whenever a new empty file is created inside the working directory with a particular extension, Incor searches for a template file with the same extension and writes the template into the newly created file.

Example:

All the empty files created in the present directory with .cpp extansion will have the contents of a.cpp, .c extansion will have the contents of a.c and .py extansion will have the contents of a.py

incor -t a

All the empty files created in the present directory with extansion in [cpp,c,py] will have the contents of template.extension if available anywhere in the path/to/the/directory

incor path/to/the/directory -t

Template Example

Using Input files

You can also add some input files in the directory where incor runs. The default input file is ‘input.txt’. Whenever a program is executed and run, Incor provides the contents of the specified input file as input to the program.

Example:

All the successfully compiled and executed programs will use input.txt present in path/to/the/directory or in any of it’s sub-directories as input

incor path/to/the/directory -i

All the successfully compiled and executed programs will use a.txt present in the current working directory or in any of it’s sub-directories as input

incor -i a.txt

Demo

Youtube link

Configuring INCOR

incor can be configured for a run using these options -

-i

To specify the input file name for the to be compiled program(with extension).

-t

To specify the name of template file(without extension).

-c

To specify the C compiler to be used.

-cpp

To specify the C++ compiler to be used.

-py

To specify the python interpreter to be used.

Compiler Options

Contributors

Srivatsan R

Adarsh B

If you have an idea for a new feature that could be added, Go ahead! I will be happy to see a pull request from you!

Metadata

Release files for incor 1.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for incor 1.0.0
File Size Uploaded Provenance Actions
incor-1.0.0.tar.gz 3.3 kB Without provenance Details for incor-1.0.0.tar.gz

Release files / incor-1.0.0.tar.gz

Download URL incor-1.0.0.tar.gz
Size 3.3 kB
Tags Source
SHA-256 checksum
How to use checksums
6c845f86e7759b01cf5e7dd3a02e5806262dd2fe403557259c75ef91ca9cae60
BLAKE2b-256 checksum
How to use checksums
2423c76ba1e8c532d4cb6b6aaa039ce252724e3c9ef18e11fd97da7a4d3ce5f0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for incor 1.0.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

1.0.0 This release

1 release file No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page