Skip to content

Commit bf52e9d

Browse files
authored
Merge pull request #9 from highcharts-for-python/develop
PR for v.1.0.0-rc1
2 parents d4e7414 + 0b19f1b commit bf52e9d

File tree

1,480 files changed

+307177
-2
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

1,480 files changed

+307177
-2
lines changed
Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
name: Bug report
3+
about: File a bug report to help us improve
4+
title: BUG
5+
labels: bug
6+
assignees: hcpchris
7+
8+
---
9+
10+
**Describe the bug**
11+
A clear and concise description of what the bug is.
12+
13+
**To Reproduce**
14+
Steps to reproduce the behavior:
15+
1. When I attempt '...' using the following code: '...'
16+
2. I receive '...'
17+
18+
**Expected behavior**
19+
A clear and concise description of what you expected to happen.
20+
21+
**Your Environment:**
22+
- OS: [e.g. Linux, Windows, etc.]
23+
- Python Version: [e.g. 3.10, 3.8, 3.11]
24+
- Highcharts JavaScript Version: [e.g. 10.2, 10.3, etc.]
25+
26+
**Additional context**
27+
Add any other context about the problem here.

.github/workflows/pypi-publish.yml

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
# This workflow uses actions that are not certified by GitHub.
2+
# They are provided by a third-party and are governed by
3+
# separate terms of service, privacy policy, and support
4+
# documentation.
5+
6+
# GitHub recommends pinning actions to a commit SHA.
7+
# To get a newer version, you will need to update the SHA.
8+
# You can also reference a tag or branch, but the action may change without warning.
9+
10+
name: Release Library to PyPi
11+
12+
on:
13+
release:
14+
types: [published]
15+
16+
env:
17+
HATCH_INDEX_USER: __token__
18+
HATCH_INDEX_AUTH: ${{ secrets.PYPI_API_TOKEN }}
19+
HATCH_INDEX_REPO: main
20+
21+
jobs:
22+
deploy:
23+
runs-on: ubuntu-latest
24+
steps:
25+
- uses: actions/checkout@v3
26+
- name: Set up Python
27+
uses: actions/setup-python@v4
28+
with:
29+
python-version: '3.x'
30+
- name: Install dependencies
31+
run: |
32+
python -m pip install --upgrade pip
33+
pip install hatch
34+
- name: Build package
35+
run: hatch build
36+
- name: Publish package
37+
run: hatch publish
Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
# This workflow uses actions that are not certified by GitHub.
2+
# They are provided by a third-party and are governed by
3+
# separate terms of service, privacy policy, and support
4+
# documentation.
5+
6+
# GitHub recommends pinning actions to a commit SHA.
7+
# To get a newer version, you will need to update the SHA.
8+
# You can also reference a tag or branch, but the action may change without warning.
9+
10+
name: Test Release Library to PyPi
11+
12+
on:
13+
pull_request:
14+
branches:
15+
- master
16+
17+
env:
18+
HATCH_INDEX_USER: __token__
19+
HATCH_INDEX_AUTH: ${{ secrets.TEST_PYPI_API_TOKEN }}
20+
HATCH_INDEX_REPO: test
21+
22+
jobs:
23+
deploy:
24+
runs-on: ubuntu-latest
25+
steps:
26+
- uses: actions/checkout@v3
27+
- name: Set up Python
28+
uses: actions/setup-python@v4
29+
with:
30+
python-version: '3.x'
31+
- name: Install dependencies
32+
run: |
33+
python -m pip install --upgrade pip
34+
pip install hatch
35+
- name: Build package
36+
run: hatch build
37+
- name: Publish package
38+
run: hatch publish

.gitignore

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,7 @@ coverage.xml
5050
*.py,cover
5151
.hypothesis/
5252
.pytest_cache/
53+
tests/pytest.ini
5354

5455
# Translations
5556
*.mo
@@ -127,3 +128,10 @@ dmypy.json
127128

128129
# Pyre type checker
129130
.pyre/
131+
132+
# VENV
133+
.py310/
134+
135+
# temp files
136+
~$*.*
137+
# tests/input_files/headless_export/output/

.readthedocs.yaml

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
# .readthedocs.yaml
2+
# Read the Docs configuration file
3+
# See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
4+
5+
# Required
6+
version: 2
7+
8+
# Set the version of Python and other tools you might need
9+
build:
10+
os: ubuntu-22.04
11+
tools:
12+
python: "3.11"
13+
# You can also specify other tool versions:
14+
# nodejs: "19"
15+
# rust: "1.64"
16+
# golang: "1.19"
17+
18+
# Build documentation in the docs/ directory with Sphinx
19+
sphinx:
20+
configuration: docs/conf.py
21+
22+
# If using Sphinx, optionally build your docs in additional formats such as PDF
23+
# formats:
24+
# - pdf
25+
26+
# Optionally declare the Python requirements required to build your docs
27+
python:
28+
install:
29+
- requirements: requirements.dev.txt

.travis.yml

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
language: python
2+
job:
3+
include:
4+
#- python: "3.8"
5+
# env:
6+
# - TOXENV=py39
7+
# - HCP_BASIC_PYTEST=true
8+
#- python: "3.9"
9+
# env:
10+
# - TOXENV=py39
11+
# - HCP_BASIC_PYTEST=true
12+
- python: "3.10"
13+
dist: focal
14+
env: TOXENV=py310
15+
- python: "3.11"
16+
dist: bionic
17+
env: TOXENV=py311
18+
- python: "3.10"
19+
dist: focal
20+
env: TOXENV=coverage
21+
- python: "3.10"
22+
dist: focal
23+
env: TOXENV=docs
24+
os:
25+
- linux
26+
git:
27+
quiet: true
28+
29+
install:
30+
- pip install -r requirements.dev.txt
31+
before_script:
32+
- curl -Os --retry 5 https://uploader.codecov.io/latest/linux/codecov
33+
- chmod +x codecov
34+
script: tox -- -v -nauto
35+
after_success:
36+
- if [[ -e .coverage ]]; then ./codecov -t $CODECOV_TOKEN; fi

CHANGES.rst

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
Release 1.0.0-rc1
2+
=========================================
3+
4+
* First public release: **Release Candidate 1**
5+

CODE_OF_CONDUCT.md

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
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, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
6+
7+
## Our Standards
8+
9+
Examples of behavior that contributes to creating a positive environment include:
10+
11+
* Using welcoming and inclusive language
12+
* Being respectful of differing viewpoints and experiences
13+
* Gracefully accepting constructive criticism
14+
* Focusing on what is best for the community
15+
* Showing empathy towards other community members
16+
17+
Examples of unacceptable behavior by participants include:
18+
19+
* The use of sexualized language or imagery and unwelcome sexual attention or advances
20+
* Trolling, insulting/derogatory comments, and personal or political attacks
21+
* Public or private harassment
22+
* Publishing others' private information, such as a physical or electronic address, without explicit permission
23+
* Other conduct which could reasonably be considered inappropriate in a professional setting
24+
25+
## Our Responsibilities
26+
27+
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.
28+
29+
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.
30+
31+
## Scope
32+
33+
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.
34+
35+
## Enforcement
36+
37+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems 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.
38+
39+
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.
40+
41+
## Attribution
42+
43+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
44+
45+
[homepage]: http://contributor-covenant.org
46+
[version]: http://contributor-covenant.org/version/1/4/

0 commit comments

Comments
 (0)