Release v0.1.0 (#1)

Release v0.1.0

.flake8

@@ -0,0 +1,9 @@
+[flake8]
+select = ANN,B,B9,C,D,E,F,W,I
+ignore = ANN101,B950,D100,D104,D107,E203,E402,E501,F401,W503,W606
+max-line-length = 80
+docstring-convention = google
+import-order-style = google
+per-file-ignores =
+ test/*:ANN,D
+ noxfile.py:ANN,D

.github/FUNDING.yml

@@ -0,0 +1,3 @@
+github: p403n1x87
+patreon: P403n1x87
+custom: ["https://www.buymeacoffee.com/Q9C1Hnm28", "https://www.paypal.me/gtornetta/1"]

.github/workflows/release.yml

@@ -0,0 +1,18 @@
+name: Release
+on:
+ release:
+ types: [published]
+jobs:
+ release:
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v2
+ - uses: actions/setup-python@v1
+ with:
+ python-version: '3.8'
+ architecture: x64
+ # - run: pip install nox==2020.5.24
+ - run: pip install poetry==1.0.5
+ # - run: nox
+ - run: poetry build
+ - run: poetry publish --username=__token__ --password=${{ secrets.PYPI_TOKEN }}

.github/workflows/tests.yml

@@ -0,0 +1,76 @@
+name: Tests
+on: push
+jobs:
+ tests:
+ runs-on: ${{ matrix.os }}
+ strategy:
+ fail-fast: false
+ matrix:
+ os: [macos-latest, ubuntu-latest, windows-latest]
+ name: Tests on ${{ matrix.os }}
+ steps:
+ - uses: actions/checkout@v2
+ with:
+ path: main
+
+ - uses: actions/setup-python@v2
+ with:
+ python-version: '3.x'
+ architecture: x64
+
+ - name: Checkout Austin development branch
+ uses: actions/checkout@master
+ with:
+ repository: P403n1x87/austin
+ ref: devel
+ path: austin
+
+ - name: Compile Austin on Linux
+ run: |
+ cd $GITHUB_WORKSPACE/austin
+ gcc -Wall -O3 -Os -s -pthread src/*.c -o src/austin
+ if: startsWith(matrix.os, 'ubuntu')
+
+ - name: Compile Austin on Windows
+ run: |
+ cd $env:GITHUB_WORKSPACE/austin
+ gcc.exe -O3 -o src/austin.exe src/*.c -lpsapi -Wall -Os -s
+ if: startsWith(matrix.os, 'windows')
+
+ - name: Compile Austin on macOS
+ run: |
+ cd $GITHUB_WORKSPACE/austin
+ gcc -Wall -O3 -Os src/*.c -o src/austin
+ if: startsWith(matrix.os, 'macos')
+
+ - run: pip install nox==2020.5.24
+ - run: pip install poetry==1.0.5
+
+ - name: Run nox on Linux
+ run: |
+ cd $GITHUB_WORKSPACE/main
+ export PATH="$GITHUB_WORKSPACE/austin/src:$PATH"
+ nox
+ if: "startsWith(matrix.os, 'ubuntu')"
+
+ - name: Run nox on macOS
+ run: |
+ cd $GITHUB_WORKSPACE/main
+ export PATH="$GITHUB_WORKSPACE/austin/src:$PATH"
+ sudo nox
+ if: startsWith(matrix.os, 'macos')
+
+ - name: Run nox on Windows
+ run: |
+ cd $env:GITHUB_WORKSPACE/main
+ $env:PATH="$env:GITHUB_WORKSPACE/austin/src;$env:PATH"
+ nox
+ if: "startsWith(matrix.os, 'windows')"
+
+ - name: Publish coverage metrics
+ run: |
+ cd $GITHUB_WORKSPACE/main
+ nox -rs coverage
+ if: startsWith(matrix.os, 'ubuntu')
+ env:
+ CODECOV_TOKEN: ${{secrets.CODECOV_TOKEN}}

.gitignore

@@ -0,0 +1,82 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+# Usually these files are written by a python script from a template
+# before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Sphinx documentation
+docs/_build/
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Nox
+.nox

.travis.yml

@@ -0,0 +1,36 @@
+language: python
+os: linux
+
+git:
+ depth: 1
+
+osx_image: xcode10
+
+dist: bionic
+
+jobs:
+ include:
+ # Linux
+ - env: TARGET=x86_64-unknown-linux-gnu
+ os: linux
+
+before_script:
+ # Install required Python versions
+ - sudo add-apt-repository ppa:deadsnakes/ppa -y
+ - sudo apt install python3.{6..9} python3.{6..9}-dev -y;
+
+ # Clone Austin development branch
+ - git clone --branch devel --depth 1 https://github.com/P403n1x87/austin.git ../austin
+
+ # Compile Austin
+ - cd ../austin
+ - gcc -Wall -O3 -Os -s -pthread src/*.c -o src/austin
+ - cd -
+
+ - pip install nox==2020.5.24
+ - pip install poetry==1.0.5
+
+script:
+ - export PATH="../austin/src:$PATH"
+ - nox
+ # nox -rs coverage

CODE-OF-CONDUCT.md

@@ -0,0 +1,73 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [INSERT EMAIL ADDRESS]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org

CONTRIBUTING.md

@@ -0,0 +1,38 @@
+# Contributing to Austin
+
+Thanks for taking the time to contribute or considering doing so.
+
+The following is a set of guidelines for contributing to Austin TUI.
+
+## Preamble
+
+TBD
+
+
+## The Coding Style
+
+TBD
+
+
+## Opening PRs
+
+Everybody is more than welcome to open a PR to fix a bug/propose enhancements/
+implement missing features. If you do, please adhere to the following
+styleguides as much as possible.
+
+
+### Git Commit Messages
+
+This styleguide is taken from the Atom project.
+
+* Use the present tense ("Add feature" not "Added feature")
+* Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
+* Limit the first line to 72 characters or less
+* Reference issues and pull requests liberally after the first line
+
+
+### Labels
+
+When opening a new PR, please apply a label to them. Try to use existing labels
+as much as possible and only create a new one if the current ones are not
+applicable.

ISSUE_TEMPLATE.md

@@ -0,0 +1,26 @@
+### Description
+
+[Description of the issue]
+
+### Steps to Reproduce
+
+1. [First Step]
+2. [Second Step]
+3. [and so on...]
+
+**Expected behavior:** [What you expect to happen]
+
+**Actual behavior:** [What actually happens]
+
+**Reproduces how often:** [What percentage of the time does it reproduce?]
+
+### Versions
+
+You can get this information from copy and pasting the output of `austin
+--version` from the command line. Also, please include the OS and what version
+of the OS you're running.
+
+### Additional Information
+
+Any additional information, configuration or data that might be necessary to
+reproduce the issue.