a9x-webstatistics 0.1.5__tar.gz

a9x_webstatistics-0.1.5/LICENSE

@@ -0,0 +1,12 @@
+COPYRIGHT AND PERMISSION NOTICE
+
+Copyright (c) 2024, Andre von Arx, andrevonarx@bluewin.ch, and many contributors, see the THANKS file.
+
+All rights reserved.
+
+Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization of the copyright holder.
+

a9x_webstatistics-0.1.5/MANIFEST.in

@@ -0,0 +1,5 @@
+include pyproject.toml
+include *.md
+include LICENSE
+include dist_del
+recursive-include tests test*.py

a9x_webstatistics-0.1.5/PKG-INFO

@@ -0,0 +1,298 @@
+Metadata-Version: 2.1
+Name: a9x_webstatistics
+Version: 0.1.5
+Summary: Web Statistics and Analytics Package
+Home-page: https://github.com/ava007/a9x-webstatistics
+Author: André von Arx
+Author-email: andrevonarx@bluewin.ch
+Project-URL: Documentation, https://github.com/ava007/a9x-webstatistics
+Project-URL: Bug Reports, https://github.com/ava007/a9x-webstatistics/issues
+Project-URL: Source Code, https://github.com/ava007/a9x-webstatistics
+Keywords: webstats,statistics,analytics
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Intended Audience :: Developers
+Classifier: Topic :: Software Development :: Build Tools
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.7
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: dev
+Requires-Dist: check-manifest; extra == "dev"
+
+# Web Statistics and Analytics
+
+This package produces web statics and analytical output based on nginx access log files.
+
+[![PyPI package](https://img.shields.io/badge/pip%20install-example--pypi--package-brightgreen)](https://pypi.org/project/a9x-webstatistics/) [![version number](https://img.shields.io/pypi/v/example-pypi-package?color=green&label=version)](https://github.com/ava007/a9x-webstatistics/releases) [![Actions Status](https://github.com/ava007/a9x-webstatistics/workflows/Test/badge.svg)](https://github.com/ava007/a9x-webstatistics/actions) [![License](https://img.shields.io/github/license/ava007/a9x-webstatistics)](https://github.com/ava007/a9x-webstatistics/blob/main/LICENSE)
+
+## Installation
+
+```bash
+pip install a9x-webstatistics
+```
+
+
+<details>
+----------------
+## old content from template starts here
+
+[![PyPI package](https://img.shields.io/badge/pip%20install-example--pypi--package-brightgreen)](https://pypi.org/project/example-pypi-package/) [![version number](https://img.shields.io/pypi/v/example-pypi-package?color=green&label=version)](https://github.com/tomchen/example_pypi_package/releases) [![Actions Status](https://github.com/tomchen/example_pypi_package/workflows/Test/badge.svg)](https://github.com/tomchen/example_pypi_package/actions) [![License](https://img.shields.io/github/license/tomchen/example_pypi_package)](https://github.com/tomchen/example_pypi_package/blob/main/LICENSE)
+
+This is an example [PyPI](https://pypi.org/) (Python Package Index) package set up with automated tests and package publishing workflow using GitHub Actions CI/CD. It is made primarily for GitHub + VS Code (Windows / Mac / Linux) users who are about to write and publish their first PyPI package. The package could serve as a starter / boilerplate / demo and the tutorial could give you a quick and concise explaination to solve some small but annoying problems you might encounter, such as package / module name confusion, and VS Code test configuration issues.
+<summary><strong>Differences from pypa/sampleproject (click to show/hide)</strong></summary>
+
+This example package is inspired by / based on the [official sample project pypa/sampleproject](https://github.com/pypa/sampleproject), but this package:
+
+- is a simplified version of pypa/sampleproject (and the [official Python Packaging User Guide](https://packaging.python.org/))
+- uses GitHub Actions for both testing and publishing, instead of Travis CI
+- is tested when pushing `master` or `main` branch, and is published when create a release
+- includes test files in the source distribution
+- uses **setup.cfg** for [version single-sourcing](https://packaging.python.org/guides/single-sourcing-package-version/) (setuptools 46.4.0+)
+- has **.vscode\settings.json** and **vscode.env** which adds **src/** folder to `PYTHONPATH`, so that test files don't have linting errors and may run with pytest in VS Code
+- does not use flake8 for automated linting - it is sometimes too strict and inflexible, you may use pylint locally instead
+- has this tutorial that covers everything you need to know in one page. Everything that might not be very useful, is hidden in collapsible sections that you can click to show
+- has **[.editorconfig](https://editorconfig.org/#download)** file
+
+
+
+## Make necessary changes
+
+### Use as a template
+
+[![Use the template](https://img.shields.io/static/v1?label=&message=Click%20here%20to%20use%20this%20package%20as%20a%20template%20to%20start%20a%20new%20repo%20on%20GitHub&color=brightgreen&style=for-the-badge)](https://github.com/tomchen/example_pypi_package/generate)
+
+(Click the above button to use this example package as a template for your new GitHub repo, this will initialize a new repository and my commits will not be in your git history)
+
+(If you do not use GitHub, you can [download the archive of the example package](https://github.com/tomchen/example_pypi_package/archive/main.zip))
+
+### Package, module name
+
+Many use a same package and module name, you could definitely do that. But this example package and its module's names are different: `example_pypi_package` and `examplepy`.
+
+Open `example_pypi_package` folder with Visual Studio Code, <kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>F</kbd> (Windows / Linux) or <kbd>Cmd</kbd> + <kbd>Shift</kbd> + <kbd>F</kbd> (MacOS) to find all occurrences of both names and replace them with your package and module's names. Also remember to change the name of the folder **src/examplepy**.
+
+Simply and very roughly speaking, package name is used in `pip install <PACKAGENAME>` and module name is used in `import <MODULENAME>`. Both names should consist of lowercase basic letters (a-z). They may have underscores (`_`) if you really need them. Hyphen-minus (`-`) should not be used.
+
+You'll also need to make sure the URL "https://pypi.org/project/example-pypi-package/" (replace `example-pypi-package` by your package name, with all `_` becoming `-`) is not occupied.
+
+<details><summary><strong>Details on naming convention (click to show/hide)</strong></summary>
+
+Underscores (`_`) can be used but such use is discouraged. Numbers can be used if the name does not start with a number, but such use is also discouraged.
+
+Name starting with a number and/or containing hyphen-minus (`-`) should not be used: although technically legal, such name causes a lot of trouble − users have to use `importlib` to import it.
+
+Don't be fooled by the URL "[pypi.org/project/example-pypi-package/](https://pypi.org/project/example-pypi-package/)" and the name "example-pypi-package" on pypi.org. pypi.org and pip system convert all `_` to `-` and use the latter on the website / in `pip` command, but the real name is still with `_`, which users should use when importing the package.
+
+There's also [namespace](https://packaging.python.org/guides/packaging-namespace-packages/) to use if you need sub-packages.
+
+</details>
+
+### Other changes
+
+Make necessary changes in **setup.py**.
+
+The package's version number `__version__` is in **src/examplepy/\_\_init\_\_.py**. You may want to change that.
+
+The example package is designed to be compatible with Python 3.6, 3.7, 3.8, 3.9, and will be tested against these versions. If you need to change the version range, you should change:
+
+- `classifiers`, `python_requires` in **setup.py**
+- `envlist` in **tox.ini**
+- `matrix: python:` in **.github/workflows/test.yml**
+
+If you plan to upload to [TestPyPI](https://test.pypi.org/) which is a playground of [PyPI](https://pypi.org/) for testing purpose, change `twine upload --repository pypi dist/*` to `twine upload --repository testpypi dist/*` in the file **.github/workflows/release.yml**.
+
+## Development
+
+### pip
+
+pip is a Python package manager. You already have pip if you use Python 3.4 and later version which include it by default. Read [this](https://pip.pypa.io/en/stable/installing/#do-i-need-to-install-pip) to know how to check whether pip is installed. Read [this](https://pip.pypa.io/en/stable/installing/#installing-with-get-pip-py) if you need to install it.
+
+### Use VS Code
+
+Visual Studio Code is the most popular code editor today, our example package is configured to work with VS Code.
+
+Install VS Code extension "[Python](https://marketplace.visualstudio.com/items?itemName=ms-python.python)".
+
+"Python" VS Code extension will suggest you install pylint. Also, the example package is configured to use pytest with VS Code + Python extensions, so, install pylint and pytest:
+
+```bash
+pip install pylint pytest
+```
+
+(It's likely you will be prompted to install them, if that's the case, you don't need to type and execute the command)
+
+**vscode.env**'s content is now `PYTHONPATH=/;src/;${PYTHONPATH}` which is good for Windows. If you use Linux or MacOS, you need to change it to `PYTHONPATH=/:src/:${PYTHONPATH}` (replacing `;` with `:`). If the PATH is not properly set, you'll see linting errors in test files and pytest won't be able to run **tests/test\_\*.py** files correctly.
+
+Close and reopen VS Code. You can now click the lab flask icon in the left menu and run all tests there, with pytest. pytest seems better than the standard unittest framework, it supports `unittest` thus you can keep using `import unittest` in your test files.
+
+The example package also has a **.editorconfig** file. You may install VS Code extension "[EditorConfig for VS Code](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig)" that uses the file. With current configuration, the EditorConfig tool can automatically use spaces (4 spaces for .py, 2 for others) for indentation, set `UTF-8` encoding, `LF` end of lines, trim trailing whitespaces in non Markdown files, etc.
+
+In VS Code, you can go to File -> Preferences -> Settings, type "Python Formatting Provider" in the search box, and choose one of the three Python code formatting tools (autopep8, black and yapf), you'll be prompted to install it. The shortcuts for formatting of a code file are <kbd>Shift</kbd> + <kbd>Alt</kbd> + <kbd>F</kbd> (Windows); <kbd>Shift</kbd> + <kbd>Option (Alt)</kbd> + <kbd>F</kbd> (MacOS); <kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>I</kbd> (Linux).
+
+### Write your package
+
+In **src/examplepy/** (`examplepy` should have been replaced by your module name) folder, rename **module1.py** and write your code in it. Add more module .py files if you need to.
+
+### Write your tests
+
+In **tests/** folder, rename **test_module1.py** (to **test\_\*.py**) and write your unit test code (with [unittest](https://docs.python.org/3/library/unittest.html)) in it. Add more **test\_\*.py** files if you need to.
+
+<details><summary><strong>The testing tool `tox` will be used in the automation with GitHub Actions CI/CD. If you want to use `tox` locally, click to read the "Use tox locally" section</strong></summary>
+
+### Use tox locally
+
+Install tox and run it:
+
+```bash
+pip install tox
+tox
+```
+
+In our configuration, tox runs a check of source distribution using [check-manifest](https://pypi.org/project/check-manifest/) (which requires your repo to be git-initialized (`git init`) and added (`git add .`) at least), setuptools's check, and unit tests using pytest. You don't need to install check-manifest and pytest though, tox will install them in a separate environment.
+
+The automated tests are run against several Python versions, but on your machine, you might be using only one version of Python, if that is Python 3.9, then run:
+
+```bash
+tox -e py39
+```
+
+</details>
+
+If you add more files to the root directory (**example_pypi_package/**), you'll need to add your file to `check-manifest --ignore` list in **tox.ini**.
+
+<details><summary><strong>Thanks to GitHub Actions' automated process, you don't need to generate distribution files locally. But if you insist, click to read the "Generate distribution files" section</strong></summary>
+
+## Generate distribution files
+
+### Install tools
+
+Install or upgrade `setuptools` and `wheel`:
+
+```bash
+python -m pip install --user --upgrade setuptools wheel
+```
+
+(If `python3` is the command on your machine, change `python` to `python3` in the above command, or add a line `alias python=python3` to **~/.bashrc** or **~/.bash_aliases** file if you use bash on Linux)
+
+### Generate `dist`
+
+From `example_pypi_package` directory, run the following command, in order to generate production version for source distribution (sdist) in `dist` folder:
+
+```bash
+python setup.py sdist bdist_wheel
+```
+
+### Install locally
+
+Optionally, you can install dist version of your package locally before uploading to [PyPI](https://pypi.org/) or [TestPyPI](https://test.pypi.org/):
+
+```bash
+pip install dist/example_pypi_package-0.1.0.tar.gz
+```
+
+(You may need to uninstall existing package first:
+
+```bash
+pip uninstall example_pypi_package
+```
+
+There may be several installed packages with the same name, so run `pip uninstall` multiple times until it says no more package to remove.)
+
+</details>
+
+## Upload to PyPI
+
+### Register on PyPI and get token
+
+Register an account on [PyPI](https://pypi.org/), go to [Account settings § API tokens](https://pypi.org/manage/account/#api-tokens), "Add API token". The PyPI token only appears once, copy it somewhere. If you missed it, delete the old and add a new token.
+
+(Register a [TestPyPI](https://test.pypi.org/) account if you are uploading to TestPyPI)
+
+### Set secret in GitHub repo
+
+On the page of your newly created or existing GitHub repo, click **Settings** -> **Secrets** -> **New repository secret**, the **Name** should be `PYPI_API_TOKEN` and the **Value** should be your PyPI token (which starts with `pypi-`).
+
+### Push or release
+
+The example package has automated tests and upload (publishing) already set up with GitHub Actions:
+
+- Every time you `git push` or a pull request is submitted on your `master` or `main` branch, the package is automatically tested against the desired Python versions with GitHub Actions.
+- Every time a new release (either the initial version or an updated version) is created, the latest version of the package is automatically uploaded to PyPI with GitHub Actions.
+
+### View it on pypi.org
+
+After your package is published on PyPI, go to [https://pypi.org/project/example-pypi-package/](https://pypi.org/project/example-pypi-package/) (`_` becomes `-`). Copy the command on the page, execute it to download and install your package from PyPI. (or test.pypi.org if you use that)
+
+If you want to modify the description / README of your package on pypi.org, you have to publish a new version.
+
+<details><summary><strong>If you publish your package to PyPI manually, click to read</strong></summary>
+
+### Install Twine
+
+Install or upgrade Twine:
+
+```bash
+python -m pip install --user --upgrade twine
+```
+
+Create a **.pypirc** file in your **$HOME** (**~**) directory, its content should be:
+
+```ini
+[pypi]
+username = __token__
+password = <PyPI token>
+```
+
+(Use `[testpypi]` instead of `[pypi]` if you are uploading to [TestPyPI](https://test.pypi.org/))
+
+Replace `<PyPI token>` with your real PyPI token (which starts with `pypi-`).
+
+(if you don't manually create **$HOME/.pypirc**, you will be prompted for a username (which should be `__token__`) and password (which should be your PyPI token) when you run Twine)
+
+### Upload
+
+Run Twine to upload all of the archives under **dist** folder:
+
+```bash
+python -m twine upload --repository pypi dist/*
+```
+
+(use `testpypi` instead of `pypi` if you are uploading to [TestPyPI](https://test.pypi.org/))
+
+### Update
+
+When you finished developing a newer version of your package, do the following things.
+
+Modify the version number `__version__` in **src\examplepy\_\_init\_\_.py**.
+
+Delete all old versions in **dist**.
+
+Run the following command again to regenerate **dist**:
+
+```bash
+python setup.py sdist bdist_wheel
+```
+
+Run the following command again to upload **dist**:
+
+```bash
+python -m twine upload --repository pypi dist/*
+```
+
+(use `testpypi` instead of `pypi` if needed)
+
+</details>
+
+## References
+
+- [Python Packaging Authority (PyPA)'s sample project](https://github.com/pypa/sampleproject)
+- [PyPA's Python Packaging User Guide](https://packaging.python.org/tutorials/packaging-projects/)
+- [Stackoverflow questions and answers](https://stackoverflow.com/questions/41093648/how-to-test-that-pypi-install-will-work-before-pushing-to-pypi-python)
+- [GitHub Actions Guides: Building and testing Python](https://docs.github.com/en/free-pro-team@latest/actions/guides/building-and-testing-python)
+
+
+</details>

a9x_webstatistics-0.1.5/README.md

@@ -0,0 +1,273 @@
+# Web Statistics and Analytics
+
+This package produces web statics and analytical output based on nginx access log files.
+
+[![PyPI package](https://img.shields.io/badge/pip%20install-example--pypi--package-brightgreen)](https://pypi.org/project/a9x-webstatistics/) [![version number](https://img.shields.io/pypi/v/example-pypi-package?color=green&label=version)](https://github.com/ava007/a9x-webstatistics/releases) [![Actions Status](https://github.com/ava007/a9x-webstatistics/workflows/Test/badge.svg)](https://github.com/ava007/a9x-webstatistics/actions) [![License](https://img.shields.io/github/license/ava007/a9x-webstatistics)](https://github.com/ava007/a9x-webstatistics/blob/main/LICENSE)
+
+## Installation
+
+```bash
+pip install a9x-webstatistics
+```
+
+
+<details>
+----------------
+## old content from template starts here
+
+[![PyPI package](https://img.shields.io/badge/pip%20install-example--pypi--package-brightgreen)](https://pypi.org/project/example-pypi-package/) [![version number](https://img.shields.io/pypi/v/example-pypi-package?color=green&label=version)](https://github.com/tomchen/example_pypi_package/releases) [![Actions Status](https://github.com/tomchen/example_pypi_package/workflows/Test/badge.svg)](https://github.com/tomchen/example_pypi_package/actions) [![License](https://img.shields.io/github/license/tomchen/example_pypi_package)](https://github.com/tomchen/example_pypi_package/blob/main/LICENSE)
+
+This is an example [PyPI](https://pypi.org/) (Python Package Index) package set up with automated tests and package publishing workflow using GitHub Actions CI/CD. It is made primarily for GitHub + VS Code (Windows / Mac / Linux) users who are about to write and publish their first PyPI package. The package could serve as a starter / boilerplate / demo and the tutorial could give you a quick and concise explaination to solve some small but annoying problems you might encounter, such as package / module name confusion, and VS Code test configuration issues.
+<summary><strong>Differences from pypa/sampleproject (click to show/hide)</strong></summary>
+
+This example package is inspired by / based on the [official sample project pypa/sampleproject](https://github.com/pypa/sampleproject), but this package:
+
+- is a simplified version of pypa/sampleproject (and the [official Python Packaging User Guide](https://packaging.python.org/))
+- uses GitHub Actions for both testing and publishing, instead of Travis CI
+- is tested when pushing `master` or `main` branch, and is published when create a release
+- includes test files in the source distribution
+- uses **setup.cfg** for [version single-sourcing](https://packaging.python.org/guides/single-sourcing-package-version/) (setuptools 46.4.0+)
+- has **.vscode\settings.json** and **vscode.env** which adds **src/** folder to `PYTHONPATH`, so that test files don't have linting errors and may run with pytest in VS Code
+- does not use flake8 for automated linting - it is sometimes too strict and inflexible, you may use pylint locally instead
+- has this tutorial that covers everything you need to know in one page. Everything that might not be very useful, is hidden in collapsible sections that you can click to show
+- has **[.editorconfig](https://editorconfig.org/#download)** file
+
+
+
+## Make necessary changes
+
+### Use as a template
+
+[![Use the template](https://img.shields.io/static/v1?label=&message=Click%20here%20to%20use%20this%20package%20as%20a%20template%20to%20start%20a%20new%20repo%20on%20GitHub&color=brightgreen&style=for-the-badge)](https://github.com/tomchen/example_pypi_package/generate)
+
+(Click the above button to use this example package as a template for your new GitHub repo, this will initialize a new repository and my commits will not be in your git history)
+
+(If you do not use GitHub, you can [download the archive of the example package](https://github.com/tomchen/example_pypi_package/archive/main.zip))
+
+### Package, module name
+
+Many use a same package and module name, you could definitely do that. But this example package and its module's names are different: `example_pypi_package` and `examplepy`.
+
+Open `example_pypi_package` folder with Visual Studio Code, <kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>F</kbd> (Windows / Linux) or <kbd>Cmd</kbd> + <kbd>Shift</kbd> + <kbd>F</kbd> (MacOS) to find all occurrences of both names and replace them with your package and module's names. Also remember to change the name of the folder **src/examplepy**.
+
+Simply and very roughly speaking, package name is used in `pip install <PACKAGENAME>` and module name is used in `import <MODULENAME>`. Both names should consist of lowercase basic letters (a-z). They may have underscores (`_`) if you really need them. Hyphen-minus (`-`) should not be used.
+
+You'll also need to make sure the URL "https://pypi.org/project/example-pypi-package/" (replace `example-pypi-package` by your package name, with all `_` becoming `-`) is not occupied.
+
+<details><summary><strong>Details on naming convention (click to show/hide)</strong></summary>
+
+Underscores (`_`) can be used but such use is discouraged. Numbers can be used if the name does not start with a number, but such use is also discouraged.
+
+Name starting with a number and/or containing hyphen-minus (`-`) should not be used: although technically legal, such name causes a lot of trouble − users have to use `importlib` to import it.
+
+Don't be fooled by the URL "[pypi.org/project/example-pypi-package/](https://pypi.org/project/example-pypi-package/)" and the name "example-pypi-package" on pypi.org. pypi.org and pip system convert all `_` to `-` and use the latter on the website / in `pip` command, but the real name is still with `_`, which users should use when importing the package.
+
+There's also [namespace](https://packaging.python.org/guides/packaging-namespace-packages/) to use if you need sub-packages.
+
+</details>
+
+### Other changes
+
+Make necessary changes in **setup.py**.
+
+The package's version number `__version__` is in **src/examplepy/\_\_init\_\_.py**. You may want to change that.
+
+The example package is designed to be compatible with Python 3.6, 3.7, 3.8, 3.9, and will be tested against these versions. If you need to change the version range, you should change:
+
+- `classifiers`, `python_requires` in **setup.py**
+- `envlist` in **tox.ini**
+- `matrix: python:` in **.github/workflows/test.yml**
+
+If you plan to upload to [TestPyPI](https://test.pypi.org/) which is a playground of [PyPI](https://pypi.org/) for testing purpose, change `twine upload --repository pypi dist/*` to `twine upload --repository testpypi dist/*` in the file **.github/workflows/release.yml**.
+
+## Development
+
+### pip
+
+pip is a Python package manager. You already have pip if you use Python 3.4 and later version which include it by default. Read [this](https://pip.pypa.io/en/stable/installing/#do-i-need-to-install-pip) to know how to check whether pip is installed. Read [this](https://pip.pypa.io/en/stable/installing/#installing-with-get-pip-py) if you need to install it.
+
+### Use VS Code
+
+Visual Studio Code is the most popular code editor today, our example package is configured to work with VS Code.
+
+Install VS Code extension "[Python](https://marketplace.visualstudio.com/items?itemName=ms-python.python)".
+
+"Python" VS Code extension will suggest you install pylint. Also, the example package is configured to use pytest with VS Code + Python extensions, so, install pylint and pytest:
+
+```bash
+pip install pylint pytest
+```
+
+(It's likely you will be prompted to install them, if that's the case, you don't need to type and execute the command)
+
+**vscode.env**'s content is now `PYTHONPATH=/;src/;${PYTHONPATH}` which is good for Windows. If you use Linux or MacOS, you need to change it to `PYTHONPATH=/:src/:${PYTHONPATH}` (replacing `;` with `:`). If the PATH is not properly set, you'll see linting errors in test files and pytest won't be able to run **tests/test\_\*.py** files correctly.
+
+Close and reopen VS Code. You can now click the lab flask icon in the left menu and run all tests there, with pytest. pytest seems better than the standard unittest framework, it supports `unittest` thus you can keep using `import unittest` in your test files.
+
+The example package also has a **.editorconfig** file. You may install VS Code extension "[EditorConfig for VS Code](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig)" that uses the file. With current configuration, the EditorConfig tool can automatically use spaces (4 spaces for .py, 2 for others) for indentation, set `UTF-8` encoding, `LF` end of lines, trim trailing whitespaces in non Markdown files, etc.
+
+In VS Code, you can go to File -> Preferences -> Settings, type "Python Formatting Provider" in the search box, and choose one of the three Python code formatting tools (autopep8, black and yapf), you'll be prompted to install it. The shortcuts for formatting of a code file are <kbd>Shift</kbd> + <kbd>Alt</kbd> + <kbd>F</kbd> (Windows); <kbd>Shift</kbd> + <kbd>Option (Alt)</kbd> + <kbd>F</kbd> (MacOS); <kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>I</kbd> (Linux).
+
+### Write your package
+
+In **src/examplepy/** (`examplepy` should have been replaced by your module name) folder, rename **module1.py** and write your code in it. Add more module .py files if you need to.
+
+### Write your tests
+
+In **tests/** folder, rename **test_module1.py** (to **test\_\*.py**) and write your unit test code (with [unittest](https://docs.python.org/3/library/unittest.html)) in it. Add more **test\_\*.py** files if you need to.
+
+<details><summary><strong>The testing tool `tox` will be used in the automation with GitHub Actions CI/CD. If you want to use `tox` locally, click to read the "Use tox locally" section</strong></summary>
+
+### Use tox locally
+
+Install tox and run it:
+
+```bash
+pip install tox
+tox
+```
+
+In our configuration, tox runs a check of source distribution using [check-manifest](https://pypi.org/project/check-manifest/) (which requires your repo to be git-initialized (`git init`) and added (`git add .`) at least), setuptools's check, and unit tests using pytest. You don't need to install check-manifest and pytest though, tox will install them in a separate environment.
+
+The automated tests are run against several Python versions, but on your machine, you might be using only one version of Python, if that is Python 3.9, then run:
+
+```bash
+tox -e py39
+```
+
+</details>
+
+If you add more files to the root directory (**example_pypi_package/**), you'll need to add your file to `check-manifest --ignore` list in **tox.ini**.
+
+<details><summary><strong>Thanks to GitHub Actions' automated process, you don't need to generate distribution files locally. But if you insist, click to read the "Generate distribution files" section</strong></summary>
+
+## Generate distribution files
+
+### Install tools
+
+Install or upgrade `setuptools` and `wheel`:
+
+```bash
+python -m pip install --user --upgrade setuptools wheel
+```
+
+(If `python3` is the command on your machine, change `python` to `python3` in the above command, or add a line `alias python=python3` to **~/.bashrc** or **~/.bash_aliases** file if you use bash on Linux)
+
+### Generate `dist`
+
+From `example_pypi_package` directory, run the following command, in order to generate production version for source distribution (sdist) in `dist` folder:
+
+```bash
+python setup.py sdist bdist_wheel
+```
+
+### Install locally
+
+Optionally, you can install dist version of your package locally before uploading to [PyPI](https://pypi.org/) or [TestPyPI](https://test.pypi.org/):
+
+```bash
+pip install dist/example_pypi_package-0.1.0.tar.gz
+```
+
+(You may need to uninstall existing package first:
+
+```bash
+pip uninstall example_pypi_package
+```
+
+There may be several installed packages with the same name, so run `pip uninstall` multiple times until it says no more package to remove.)
+
+</details>
+
+## Upload to PyPI
+
+### Register on PyPI and get token
+
+Register an account on [PyPI](https://pypi.org/), go to [Account settings § API tokens](https://pypi.org/manage/account/#api-tokens), "Add API token". The PyPI token only appears once, copy it somewhere. If you missed it, delete the old and add a new token.
+
+(Register a [TestPyPI](https://test.pypi.org/) account if you are uploading to TestPyPI)
+
+### Set secret in GitHub repo
+
+On the page of your newly created or existing GitHub repo, click **Settings** -> **Secrets** -> **New repository secret**, the **Name** should be `PYPI_API_TOKEN` and the **Value** should be your PyPI token (which starts with `pypi-`).
+
+### Push or release
+
+The example package has automated tests and upload (publishing) already set up with GitHub Actions:
+
+- Every time you `git push` or a pull request is submitted on your `master` or `main` branch, the package is automatically tested against the desired Python versions with GitHub Actions.
+- Every time a new release (either the initial version or an updated version) is created, the latest version of the package is automatically uploaded to PyPI with GitHub Actions.
+
+### View it on pypi.org
+
+After your package is published on PyPI, go to [https://pypi.org/project/example-pypi-package/](https://pypi.org/project/example-pypi-package/) (`_` becomes `-`). Copy the command on the page, execute it to download and install your package from PyPI. (or test.pypi.org if you use that)
+
+If you want to modify the description / README of your package on pypi.org, you have to publish a new version.
+
+<details><summary><strong>If you publish your package to PyPI manually, click to read</strong></summary>
+
+### Install Twine
+
+Install or upgrade Twine:
+
+```bash
+python -m pip install --user --upgrade twine
+```
+
+Create a **.pypirc** file in your **$HOME** (**~**) directory, its content should be:
+
+```ini
+[pypi]
+username = __token__
+password = <PyPI token>
+```
+
+(Use `[testpypi]` instead of `[pypi]` if you are uploading to [TestPyPI](https://test.pypi.org/))
+
+Replace `<PyPI token>` with your real PyPI token (which starts with `pypi-`).
+
+(if you don't manually create **$HOME/.pypirc**, you will be prompted for a username (which should be `__token__`) and password (which should be your PyPI token) when you run Twine)
+
+### Upload
+
+Run Twine to upload all of the archives under **dist** folder:
+
+```bash
+python -m twine upload --repository pypi dist/*
+```
+
+(use `testpypi` instead of `pypi` if you are uploading to [TestPyPI](https://test.pypi.org/))
+
+### Update
+
+When you finished developing a newer version of your package, do the following things.
+
+Modify the version number `__version__` in **src\examplepy\_\_init\_\_.py**.
+
+Delete all old versions in **dist**.
+
+Run the following command again to regenerate **dist**:
+
+```bash
+python setup.py sdist bdist_wheel
+```
+
+Run the following command again to upload **dist**:
+
+```bash
+python -m twine upload --repository pypi dist/*
+```
+
+(use `testpypi` instead of `pypi` if needed)
+
+</details>
+
+## References
+
+- [Python Packaging Authority (PyPA)'s sample project](https://github.com/pypa/sampleproject)
+- [PyPA's Python Packaging User Guide](https://packaging.python.org/tutorials/packaging-projects/)
+- [Stackoverflow questions and answers](https://stackoverflow.com/questions/41093648/how-to-test-that-pypi-install-will-work-before-pushing-to-pypi-python)
+- [GitHub Actions Guides: Building and testing Python](https://docs.github.com/en/free-pro-team@latest/actions/guides/building-and-testing-python)
+
+
+</details>

a9x_webstatistics-0.1.5/dist_del

@@ -0,0 +1 @@
+

a9x_webstatistics-0.1.5/pyproject.toml

@@ -0,0 +1,4 @@
+[build-system]
+requires = ["setuptools>=46.4.0", "wheel"]
+build-backend = "setuptools.build_meta"
+# https://packaging.python.org/en/latest/guides/writing-pyproject-toml/

a9x_webstatistics-0.1.5/setup.cfg

@@ -0,0 +1,8 @@
+[metadata]
+version = attr: a9x_webstatistics.__version__
+license_files = LICENSE
+
+[egg_info]
+tag_build = 
+tag_date = 0
+

a9x_webstatistics-0.1.5/setup.py

@@ -0,0 +1,50 @@
+import setuptools
+
+with open('README.md', 'r', encoding='utf-8') as fh:
+    long_description = fh.read()
+
+setuptools.setup(
+    name='a9x_webstatistics',
+    author='André von Arx',
+    author_email='andrevonarx@bluewin.ch',
+    description='Web Statistics and Analytics Package',
+    keywords='webstats, statistics, analytics',
+    long_description=long_description,
+    long_description_content_type='text/markdown',
+    url='https://github.com/ava007/a9x-webstatistics',
+    project_urls={
+        'Documentation': 'https://github.com/ava007/a9x-webstatistics',
+        'Bug Reports':
+        'https://github.com/ava007/a9x-webstatistics/issues',
+        'Source Code': 'https://github.com/ava007/a9x-webstatistics',
+        # 'Funding': '',
+        # 'Say Thanks!': '',
+    },
+    package_dir={'': 'src'},
+    packages=setuptools.find_packages(where='src'),
+    classifiers=[
+        # see https://pypi.org/classifiers/
+        'Development Status :: 5 - Production/Stable',
+
+        'Intended Audience :: Developers',
+        'Topic :: Software Development :: Build Tools',
+
+        'Programming Language :: Python :: 3',
+        'Programming Language :: Python :: 3.9',
+        'Programming Language :: Python :: 3 :: Only',
+        'License :: OSI Approved :: MIT License',
+        'Operating System :: OS Independent',
+    ],
+    python_requires='>=3.7',
+    # install_requires=['Pillow'],
+    extras_require={
+        'dev': ['check-manifest'],
+        # 'test': ['coverage'],
+    },
+    # entry_points={
+    #     'console_scripts': [  # This can provide executable scripts
+    #         'run=examplepy:main',
+    # You can execute `run` in bash to run `main()` in src/examplepy/__init__.py
+    #     ],
+    # },
+)

a9x_webstatistics-0.1.5/src/a9x_webstatistics/__init__.py

@@ -0,0 +1,5 @@
+__version__ = "0.1.5"
+
+from .module1 import *
+from .main import *
+from .updatestatistics import upd

a9x_webstatistics-0.1.5/src/a9x_webstatistics/main.py

@@ -0,0 +1,152 @@
+import argparse
+import io
+import json
+import re
+import sys
+from datetime import datetime
+from .updatestatistics import upd
+
+def parseRec(rec, log_pattern):
+    print(str(rec))
+
+    r = {}
+    # skip comments recs
+    if rec[0:1] == '#':
+        return r
+
+    match = log_pattern.match(rec)
+    if match:
+        ip_address = match.group(1)
+        timestamp = match.group(2)
+        request = match.group(3)
+        status = match.group(4)
+        bytes_sent = match.group(5)
+        referer = match.group(6)
+        user_agent = match.group(7)
+
+        dto = datetime.strptime(timestamp,'%d/%b/%Y:%H:%M:%S %z')  # 07/Jan/2024:14:06:24 +0000
+                
+        r = {
+            'ip': ip_address,
+            'ymd': dto.strftime("%Y%m%d"),
+            'timestamp': dto.strftime("%Y%m%d%H%M%S") ,
+            'request': request,
+            'status': status,
+            'bytes_sent': bytes_sent,
+            'referer': referer,
+            'user_agent': user_agent
+        }
+                
+        return r
+    
+
+    # get date and time:  19/Apr/2024:14:49:22 +0000
+    dtcomp = re.compile('\d{2}[/][A-Za-z]{3}[/]\d{4}[:]\d{2}[:]\d{2}[:]\d{2}')
+    dt = dtcomp.search(rec)  # scan for first match in rec
+    r['timestamp'] = datetime.strptime(dt[0],'%d/%b/%Y:%H:%M:%S')
+
+    # get ip address:
+    ip6 =   '''(?:(?x)(?:(?:[0-9a-f]{1,4}:){1,1}(?::[0-9a-f]{1,4}){1,6})|
+    (?:(?:[0-9a-f]{1,4}:){1,2}(?::[0-9a-f]{1,4}){1,5})|
+    (?:(?:[0-9a-f]{1,4}:){1,3}(?::[0-9a-f]{1,4}){1,4})|
+    (?:(?:[0-9a-f]{1,4}:){1,4}(?::[0-9a-f]{1,4}){1,3})|
+    (?:(?:[0-9a-f]{1,4}:){1,5}(?::[0-9a-f]{1,4}){1,2})|
+    (?:(?:[0-9a-f]{1,4}:){1,6}(?::[0-9a-f]{1,4}){1,1})|
+    (?:(?:(?:[0-9a-f]{1,4}:){1,7}|:):)|
+    (?::(?::[0-9a-f]{1,4}){1,7})|
+    (?:(?:(?:(?:[0-9a-f]{1,4}:){6})(?:25[0-5]|2[0-4]\d|[0-1]?\d?\d)(?:\.(?:25[0-5]|2[0-4]\d|[0-1]?\d?\d)){3}))|
+    (?:(?:(?:[0-9a-f]{1,4}:){5}[0-9a-f]{1,4}:(?:25[0-5]|2[0-4]\d|[0-1]?\d?\d)(?:\.(?:25[0-5]|2[0-4]\d|[0-1]?\d?\d)){3}))|
+    (?:(?:[0-9a-f]{1,4}:){5}:[0-9a-f]{1,4}:(?:25[0-5]|2[0-4]\d|[0-1]?\d?\d)(?:\.(?:25[0-5]|2[0-4]\d|[0-1]?\d?\d)){3})|
+    (?:(?:[0-9a-f]{1,4}:){1,1}(?::[0-9a-f]{1,4}){1,4}:(?:25[0-5]|2[0-4]\d|[0-1]?\d?\d)(?:\.(?:25[0-5]|2[0-4]\d|[0-1]?\d?\d)){3})|
+    (?:(?:[0-9a-f]{1,4}:){1,2}(?::[0-9a-f]{1,4}){1,3}:(?:25[0-5]|2[0-4]\d|[0-1]?\d?\d)(?:\.(?:25[0-5]|2[0-4]\d|[0-1]?\d?\d)){3})|
+    (?:(?:[0-9a-f]{1,4}:){1,3}(?::[0-9a-f]{1,4}){1,2}:(?:25[0-5]|2[0-4]\d|[0-1]?\d?\d)(?:\.(?:25[0-5]|2[0-4]\d|[0-1]?\d?\d)){3})|
+    (?:(?:[0-9a-f]{1,4}:){1,4}(?::[0-9a-f]{1,4}){1,1}:(?:25[0-5]|2[0-4]\d|[0-1]?\d?\d)(?:\.(?:25[0-5]|2[0-4]\d|[0-1]?\d?\d)){3})|
+    (?:(?:(?:[0-9a-f]{1,4}:){1,5}|:):(?:25[0-5]|2[0-4]\d|[0-1]?\d?\d)(?:\.(?:25[0-5]|2[0-4]\d|[0-1]?\d?\d)){3})|
+    (?::(?::[0-9a-f]{1,4}){1,5}:(?:25[0-5]|2[0-4]\d|[0-1]?\d?\d)(?:\.(?:25[0-5]|2[0-4]\d|[0-1]?\d?\d)){3}))
+    '''
+    #ip4 =   '(?:[12]?\\d?\\d\\.){3}[12]?\\d?\\d'
+    ip4 = '^([0-9]{1,3})\.([0-9]{1,3})\.([0-9]{1,3})\.([0-9]{1,3})$'
+     
+    ip = re.findall(ip4 + '|' + ip6, rec)
+    if not ip:
+        r['ip'] = ''
+        print("IP not detected in: " + rec)
+    else:
+        r['ip'] = ip[0]
+    return r
+
+
+def detectDeviceClass(ua):
+  if ua is None:
+     return 'desktop'
+  if (ua.lower().find('bot') > 0):
+     return 'bots'
+  if (ua.lower().find('python') > 0):
+     return 'bots'
+  if (ua.lower().find('mediapartner') > 0):
+     return 'others'
+  if (ua.lower().find('curl') > 0):
+     return 'others'
+  if (ua.lower().find('ipad') > 0):
+     return 'tablet'
+  if (ua.lower().find('mobile') > 0):
+     return 'mobile'
+  if (ua.lower().find('android') > 0):
+     return 'tablet'
+  return 'desktop'
+
+def runws():
+    parser = argparse.ArgumentParser(allow_abbrev=False)
+    parser.add_argument("-s", "--statfile", help="json file that contains calculated statistics", default="webstat.json")
+    parser.add_argument("-i", "--infile", help="filename including path to web server access log that contains input data", default="nginx_access.log")
+    args, unknown = parser.parse_known_args()
+
+    # init statistic file if it does not exist:
+    d = {}
+    d['timelastrec'] = '19991231235959'
+    d['days'] = {}
+
+    lasttimerecobj = datetime.strptime(d['timelastrec'],"%Y%m%d%H%M%S")
+    print("lasttimerecobj: " + str(lasttimerecobj))
+
+    # init job results
+    j = {
+        'records_read_total': 0,
+        'records_skipped_comment': 0,
+        'records_already_processed': 0,
+        'records_processed_for_statistic': 0,
+    }
+    
+    # load statistic file if it exists
+    try:
+        f = open(args.statfile) 
+        d = json.load(f) 
+    except FileNotFoundError:   # first call: file does not exists
+        print("-s statistic file not found, it will be automatically created")
+    except json.JSONDecodeError:
+        print("-s json file is not valid")
+
+    visitIP = {}
+
+    ip_pattern = r'\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}|[0-9a-fA-F:]+'
+    log_pattern = re.compile(r'({}) - - \[([^\]]+)\] "([^"]+)" (\d+) (\d+) "([^"]+)" "([^"]+)"'.format(ip_pattern))
+    
+    # process infile:
+    with open(args.infile,'r') as infile:
+        for rec in infile:
+            recparsed = parseRec(rec, log_pattern)
+            # skip unrecognized records:
+            if not recparsed or recparsed['timestamp'] is None or recparsed['ip'] is None:
+                continue
+            # skip already processed data:
+            if recparsed['timestamp']  <=  d['timelastrec']:
+                continue
+            d = upd(d, recparsed, visitIP)
+            
+    # write updated statistic file:
+    with open(args.statfile, "w") as sf:
+       json.dump(d,sf)  
+    return 0
+
+if __name__ == "__main__":
+    runws()

a9x_webstatistics-0.1.5/src/a9x_webstatistics/module1.py

@@ -0,0 +1,22 @@
+# Example PyPI (Python Package Index) Package
+
+class Number(object):
+
+    def __init__(self, n):
+        self.value = n
+
+    def val(self):
+        return self.value
+
+    def add(self, n2):
+        self.value += n2.val()
+
+    def __add__(self, n2):
+        return self.__class__(self.value + n2.val())
+
+    def __str__(self):
+        return str(self.val())
+
+    @classmethod
+    def addall(cls, number_obj_iter):
+        cls(sum(n.val() for n in number_obj_iter))

a9x_webstatistics-0.1.5/src/a9x_webstatistics/updatestatistics.py

@@ -0,0 +1,31 @@
+def upd(
+    d,
+    i,
+    visitIP):
+        
+    dt = i['ymd']
+
+    # init a new day with minimal attributes:
+    if dt not in d['days']:
+        d['days'][dt] = {}
+        d['days'][dt]['hits']    = 0;
+        d['days'][dt]['visits']  = 0;
+        d['days'][dt]['bytes_sent'] = 0;
+        d['days'][dt]['serverResponseCode'] = {}
+
+    # update statistics
+    d['days'][dt]['hits'] = d['days'][dt]['hits'] + 1
+    d['days'][dt]['bytes_sent'] = str(int(d['days'][dt]['bytes_sent']) + int(i['bytes_sent']))
+
+    if i['status'] in d['days'][dt]['serverResponseCode']:
+        d['days'][dt]['serverResponseCode'][i['status']] += 1
+    else:
+        d['days'][dt]['serverResponseCode'][i['status']] = 1
+        
+    d['timelastrec'] = i['timestamp']
+
+    if i['ip'] not in visitIP:
+        d['days'][dt]['visits'] = d['days'][dt]['visits'] + 1;
+        visitIP[i['ip']] = 1
+        
+    return d

a9x_webstatistics-0.1.5/src/a9x_webstatistics.egg-info/PKG-INFO

@@ -0,0 +1,298 @@
+Metadata-Version: 2.1
+Name: a9x_webstatistics
+Version: 0.1.5
+Summary: Web Statistics and Analytics Package
+Home-page: https://github.com/ava007/a9x-webstatistics
+Author: André von Arx
+Author-email: andrevonarx@bluewin.ch
+Project-URL: Documentation, https://github.com/ava007/a9x-webstatistics
+Project-URL: Bug Reports, https://github.com/ava007/a9x-webstatistics/issues
+Project-URL: Source Code, https://github.com/ava007/a9x-webstatistics
+Keywords: webstats,statistics,analytics
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Intended Audience :: Developers
+Classifier: Topic :: Software Development :: Build Tools
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.7
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: dev
+Requires-Dist: check-manifest; extra == "dev"
+
+# Web Statistics and Analytics
+
+This package produces web statics and analytical output based on nginx access log files.
+
+[![PyPI package](https://img.shields.io/badge/pip%20install-example--pypi--package-brightgreen)](https://pypi.org/project/a9x-webstatistics/) [![version number](https://img.shields.io/pypi/v/example-pypi-package?color=green&label=version)](https://github.com/ava007/a9x-webstatistics/releases) [![Actions Status](https://github.com/ava007/a9x-webstatistics/workflows/Test/badge.svg)](https://github.com/ava007/a9x-webstatistics/actions) [![License](https://img.shields.io/github/license/ava007/a9x-webstatistics)](https://github.com/ava007/a9x-webstatistics/blob/main/LICENSE)
+
+## Installation
+
+```bash
+pip install a9x-webstatistics
+```
+
+
+<details>
+----------------
+## old content from template starts here
+
+[![PyPI package](https://img.shields.io/badge/pip%20install-example--pypi--package-brightgreen)](https://pypi.org/project/example-pypi-package/) [![version number](https://img.shields.io/pypi/v/example-pypi-package?color=green&label=version)](https://github.com/tomchen/example_pypi_package/releases) [![Actions Status](https://github.com/tomchen/example_pypi_package/workflows/Test/badge.svg)](https://github.com/tomchen/example_pypi_package/actions) [![License](https://img.shields.io/github/license/tomchen/example_pypi_package)](https://github.com/tomchen/example_pypi_package/blob/main/LICENSE)
+
+This is an example [PyPI](https://pypi.org/) (Python Package Index) package set up with automated tests and package publishing workflow using GitHub Actions CI/CD. It is made primarily for GitHub + VS Code (Windows / Mac / Linux) users who are about to write and publish their first PyPI package. The package could serve as a starter / boilerplate / demo and the tutorial could give you a quick and concise explaination to solve some small but annoying problems you might encounter, such as package / module name confusion, and VS Code test configuration issues.
+<summary><strong>Differences from pypa/sampleproject (click to show/hide)</strong></summary>
+
+This example package is inspired by / based on the [official sample project pypa/sampleproject](https://github.com/pypa/sampleproject), but this package:
+
+- is a simplified version of pypa/sampleproject (and the [official Python Packaging User Guide](https://packaging.python.org/))
+- uses GitHub Actions for both testing and publishing, instead of Travis CI
+- is tested when pushing `master` or `main` branch, and is published when create a release
+- includes test files in the source distribution
+- uses **setup.cfg** for [version single-sourcing](https://packaging.python.org/guides/single-sourcing-package-version/) (setuptools 46.4.0+)
+- has **.vscode\settings.json** and **vscode.env** which adds **src/** folder to `PYTHONPATH`, so that test files don't have linting errors and may run with pytest in VS Code
+- does not use flake8 for automated linting - it is sometimes too strict and inflexible, you may use pylint locally instead
+- has this tutorial that covers everything you need to know in one page. Everything that might not be very useful, is hidden in collapsible sections that you can click to show
+- has **[.editorconfig](https://editorconfig.org/#download)** file
+
+
+
+## Make necessary changes
+
+### Use as a template
+
+[![Use the template](https://img.shields.io/static/v1?label=&message=Click%20here%20to%20use%20this%20package%20as%20a%20template%20to%20start%20a%20new%20repo%20on%20GitHub&color=brightgreen&style=for-the-badge)](https://github.com/tomchen/example_pypi_package/generate)
+
+(Click the above button to use this example package as a template for your new GitHub repo, this will initialize a new repository and my commits will not be in your git history)
+
+(If you do not use GitHub, you can [download the archive of the example package](https://github.com/tomchen/example_pypi_package/archive/main.zip))
+
+### Package, module name
+
+Many use a same package and module name, you could definitely do that. But this example package and its module's names are different: `example_pypi_package` and `examplepy`.
+
+Open `example_pypi_package` folder with Visual Studio Code, <kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>F</kbd> (Windows / Linux) or <kbd>Cmd</kbd> + <kbd>Shift</kbd> + <kbd>F</kbd> (MacOS) to find all occurrences of both names and replace them with your package and module's names. Also remember to change the name of the folder **src/examplepy**.
+
+Simply and very roughly speaking, package name is used in `pip install <PACKAGENAME>` and module name is used in `import <MODULENAME>`. Both names should consist of lowercase basic letters (a-z). They may have underscores (`_`) if you really need them. Hyphen-minus (`-`) should not be used.
+
+You'll also need to make sure the URL "https://pypi.org/project/example-pypi-package/" (replace `example-pypi-package` by your package name, with all `_` becoming `-`) is not occupied.
+
+<details><summary><strong>Details on naming convention (click to show/hide)</strong></summary>
+
+Underscores (`_`) can be used but such use is discouraged. Numbers can be used if the name does not start with a number, but such use is also discouraged.
+
+Name starting with a number and/or containing hyphen-minus (`-`) should not be used: although technically legal, such name causes a lot of trouble − users have to use `importlib` to import it.
+
+Don't be fooled by the URL "[pypi.org/project/example-pypi-package/](https://pypi.org/project/example-pypi-package/)" and the name "example-pypi-package" on pypi.org. pypi.org and pip system convert all `_` to `-` and use the latter on the website / in `pip` command, but the real name is still with `_`, which users should use when importing the package.
+
+There's also [namespace](https://packaging.python.org/guides/packaging-namespace-packages/) to use if you need sub-packages.
+
+</details>
+
+### Other changes
+
+Make necessary changes in **setup.py**.
+
+The package's version number `__version__` is in **src/examplepy/\_\_init\_\_.py**. You may want to change that.
+
+The example package is designed to be compatible with Python 3.6, 3.7, 3.8, 3.9, and will be tested against these versions. If you need to change the version range, you should change:
+
+- `classifiers`, `python_requires` in **setup.py**
+- `envlist` in **tox.ini**
+- `matrix: python:` in **.github/workflows/test.yml**
+
+If you plan to upload to [TestPyPI](https://test.pypi.org/) which is a playground of [PyPI](https://pypi.org/) for testing purpose, change `twine upload --repository pypi dist/*` to `twine upload --repository testpypi dist/*` in the file **.github/workflows/release.yml**.
+
+## Development
+
+### pip
+
+pip is a Python package manager. You already have pip if you use Python 3.4 and later version which include it by default. Read [this](https://pip.pypa.io/en/stable/installing/#do-i-need-to-install-pip) to know how to check whether pip is installed. Read [this](https://pip.pypa.io/en/stable/installing/#installing-with-get-pip-py) if you need to install it.
+
+### Use VS Code
+
+Visual Studio Code is the most popular code editor today, our example package is configured to work with VS Code.
+
+Install VS Code extension "[Python](https://marketplace.visualstudio.com/items?itemName=ms-python.python)".
+
+"Python" VS Code extension will suggest you install pylint. Also, the example package is configured to use pytest with VS Code + Python extensions, so, install pylint and pytest:
+
+```bash
+pip install pylint pytest
+```
+
+(It's likely you will be prompted to install them, if that's the case, you don't need to type and execute the command)
+
+**vscode.env**'s content is now `PYTHONPATH=/;src/;${PYTHONPATH}` which is good for Windows. If you use Linux or MacOS, you need to change it to `PYTHONPATH=/:src/:${PYTHONPATH}` (replacing `;` with `:`). If the PATH is not properly set, you'll see linting errors in test files and pytest won't be able to run **tests/test\_\*.py** files correctly.
+
+Close and reopen VS Code. You can now click the lab flask icon in the left menu and run all tests there, with pytest. pytest seems better than the standard unittest framework, it supports `unittest` thus you can keep using `import unittest` in your test files.
+
+The example package also has a **.editorconfig** file. You may install VS Code extension "[EditorConfig for VS Code](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig)" that uses the file. With current configuration, the EditorConfig tool can automatically use spaces (4 spaces for .py, 2 for others) for indentation, set `UTF-8` encoding, `LF` end of lines, trim trailing whitespaces in non Markdown files, etc.
+
+In VS Code, you can go to File -> Preferences -> Settings, type "Python Formatting Provider" in the search box, and choose one of the three Python code formatting tools (autopep8, black and yapf), you'll be prompted to install it. The shortcuts for formatting of a code file are <kbd>Shift</kbd> + <kbd>Alt</kbd> + <kbd>F</kbd> (Windows); <kbd>Shift</kbd> + <kbd>Option (Alt)</kbd> + <kbd>F</kbd> (MacOS); <kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>I</kbd> (Linux).
+
+### Write your package
+
+In **src/examplepy/** (`examplepy` should have been replaced by your module name) folder, rename **module1.py** and write your code in it. Add more module .py files if you need to.
+
+### Write your tests
+
+In **tests/** folder, rename **test_module1.py** (to **test\_\*.py**) and write your unit test code (with [unittest](https://docs.python.org/3/library/unittest.html)) in it. Add more **test\_\*.py** files if you need to.
+
+<details><summary><strong>The testing tool `tox` will be used in the automation with GitHub Actions CI/CD. If you want to use `tox` locally, click to read the "Use tox locally" section</strong></summary>
+
+### Use tox locally
+
+Install tox and run it:
+
+```bash
+pip install tox
+tox
+```
+
+In our configuration, tox runs a check of source distribution using [check-manifest](https://pypi.org/project/check-manifest/) (which requires your repo to be git-initialized (`git init`) and added (`git add .`) at least), setuptools's check, and unit tests using pytest. You don't need to install check-manifest and pytest though, tox will install them in a separate environment.
+
+The automated tests are run against several Python versions, but on your machine, you might be using only one version of Python, if that is Python 3.9, then run:
+
+```bash
+tox -e py39
+```
+
+</details>
+
+If you add more files to the root directory (**example_pypi_package/**), you'll need to add your file to `check-manifest --ignore` list in **tox.ini**.
+
+<details><summary><strong>Thanks to GitHub Actions' automated process, you don't need to generate distribution files locally. But if you insist, click to read the "Generate distribution files" section</strong></summary>
+
+## Generate distribution files
+
+### Install tools
+
+Install or upgrade `setuptools` and `wheel`:
+
+```bash
+python -m pip install --user --upgrade setuptools wheel
+```
+
+(If `python3` is the command on your machine, change `python` to `python3` in the above command, or add a line `alias python=python3` to **~/.bashrc** or **~/.bash_aliases** file if you use bash on Linux)
+
+### Generate `dist`
+
+From `example_pypi_package` directory, run the following command, in order to generate production version for source distribution (sdist) in `dist` folder:
+
+```bash
+python setup.py sdist bdist_wheel
+```
+
+### Install locally
+
+Optionally, you can install dist version of your package locally before uploading to [PyPI](https://pypi.org/) or [TestPyPI](https://test.pypi.org/):
+
+```bash
+pip install dist/example_pypi_package-0.1.0.tar.gz
+```
+
+(You may need to uninstall existing package first:
+
+```bash
+pip uninstall example_pypi_package
+```
+
+There may be several installed packages with the same name, so run `pip uninstall` multiple times until it says no more package to remove.)
+
+</details>
+
+## Upload to PyPI
+
+### Register on PyPI and get token
+
+Register an account on [PyPI](https://pypi.org/), go to [Account settings § API tokens](https://pypi.org/manage/account/#api-tokens), "Add API token". The PyPI token only appears once, copy it somewhere. If you missed it, delete the old and add a new token.
+
+(Register a [TestPyPI](https://test.pypi.org/) account if you are uploading to TestPyPI)
+
+### Set secret in GitHub repo
+
+On the page of your newly created or existing GitHub repo, click **Settings** -> **Secrets** -> **New repository secret**, the **Name** should be `PYPI_API_TOKEN` and the **Value** should be your PyPI token (which starts with `pypi-`).
+
+### Push or release
+
+The example package has automated tests and upload (publishing) already set up with GitHub Actions:
+
+- Every time you `git push` or a pull request is submitted on your `master` or `main` branch, the package is automatically tested against the desired Python versions with GitHub Actions.
+- Every time a new release (either the initial version or an updated version) is created, the latest version of the package is automatically uploaded to PyPI with GitHub Actions.
+
+### View it on pypi.org
+
+After your package is published on PyPI, go to [https://pypi.org/project/example-pypi-package/](https://pypi.org/project/example-pypi-package/) (`_` becomes `-`). Copy the command on the page, execute it to download and install your package from PyPI. (or test.pypi.org if you use that)
+
+If you want to modify the description / README of your package on pypi.org, you have to publish a new version.
+
+<details><summary><strong>If you publish your package to PyPI manually, click to read</strong></summary>
+
+### Install Twine
+
+Install or upgrade Twine:
+
+```bash
+python -m pip install --user --upgrade twine
+```
+
+Create a **.pypirc** file in your **$HOME** (**~**) directory, its content should be:
+
+```ini
+[pypi]
+username = __token__
+password = <PyPI token>
+```
+
+(Use `[testpypi]` instead of `[pypi]` if you are uploading to [TestPyPI](https://test.pypi.org/))
+
+Replace `<PyPI token>` with your real PyPI token (which starts with `pypi-`).
+
+(if you don't manually create **$HOME/.pypirc**, you will be prompted for a username (which should be `__token__`) and password (which should be your PyPI token) when you run Twine)
+
+### Upload
+
+Run Twine to upload all of the archives under **dist** folder:
+
+```bash
+python -m twine upload --repository pypi dist/*
+```
+
+(use `testpypi` instead of `pypi` if you are uploading to [TestPyPI](https://test.pypi.org/))
+
+### Update
+
+When you finished developing a newer version of your package, do the following things.
+
+Modify the version number `__version__` in **src\examplepy\_\_init\_\_.py**.
+
+Delete all old versions in **dist**.
+
+Run the following command again to regenerate **dist**:
+
+```bash
+python setup.py sdist bdist_wheel
+```
+
+Run the following command again to upload **dist**:
+
+```bash
+python -m twine upload --repository pypi dist/*
+```
+
+(use `testpypi` instead of `pypi` if needed)
+
+</details>
+
+## References
+
+- [Python Packaging Authority (PyPA)'s sample project](https://github.com/pypa/sampleproject)
+- [PyPA's Python Packaging User Guide](https://packaging.python.org/tutorials/packaging-projects/)
+- [Stackoverflow questions and answers](https://stackoverflow.com/questions/41093648/how-to-test-that-pypi-install-will-work-before-pushing-to-pypi-python)
+- [GitHub Actions Guides: Building and testing Python](https://docs.github.com/en/free-pro-team@latest/actions/guides/building-and-testing-python)
+
+
+</details>

a9x_webstatistics-0.1.5/src/a9x_webstatistics.egg-info/SOURCES.txt

@@ -0,0 +1,19 @@
+LICENSE
+MANIFEST.in
+README.md
+dist_del
+pyproject.toml
+setup.cfg
+setup.py
+src/a9x_webstatistics/__init__.py
+src/a9x_webstatistics/main.py
+src/a9x_webstatistics/module1.py
+src/a9x_webstatistics/updatestatistics.py
+src/a9x_webstatistics.egg-info/PKG-INFO
+src/a9x_webstatistics.egg-info/SOURCES.txt
+src/a9x_webstatistics.egg-info/dependency_links.txt
+src/a9x_webstatistics.egg-info/requires.txt
+src/a9x_webstatistics.egg-info/top_level.txt
+tests/test_main001.py
+tests/test_main010.py
+tests/test_module1.py

a9x_webstatistics-0.1.5/src/a9x_webstatistics.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

a9x_webstatistics-0.1.5/src/a9x_webstatistics.egg-info/requires.txt

@@ -0,0 +1,3 @@
+
+[dev]
+check-manifest

a9x_webstatistics-0.1.5/src/a9x_webstatistics.egg-info/top_level.txt

@@ -0,0 +1 @@
+a9x_webstatistics

a9x_webstatistics-0.1.5/tests/test_main001.py

@@ -0,0 +1,21 @@
+import unittest
+from pathlib import Path
+
+from a9x_webstatistics.main import *
+from a9x_webstatistics.updatestatistics import upd
+
+class TestMain(unittest.TestCase):
+
+    def test_main(self):
+        print("home: " + str(Path.home()) )
+        # calling runws expecting return 0
+        assert runws() == 0
+        file = Path("webstat.json")  
+        with open(file) as f:  
+            file_data = f.read()  
+        print(str(file_data))
+        contents = json.loads(file_data)
+        assert '20240130144922' in contents['timelastrec']
+
+if __name__ == '__main__':
+    unittest.main()

a9x_webstatistics-0.1.5/tests/test_main010.py

@@ -0,0 +1,20 @@
+import unittest
+from pathlib import Path
+
+from a9x_webstatistics.main import *
+from a9x_webstatistics.updatestatistics import *
+
+class TestMain010(unittest.TestCase):
+
+    def test_main010(self):
+        # calling runws expecting return 0
+        assert runws() == 0
+        file = Path("webstat.json")  
+        with open(file) as f:  
+            file_data = f.read()  
+        print(str(file_data))
+        contents = json.loads(file_data)
+        assert '20240130144922' in contents['timelastrec']
+
+if __name__ == '__main__':
+    unittest.main()

a9x_webstatistics-0.1.5/tests/test_module1.py

@@ -0,0 +1,13 @@
+import unittest
+
+from a9x_webstatistics.module1 import Number
+
+
+class TestSimple(unittest.TestCase):
+
+    def test_add(self):
+        self.assertEqual((Number(7) + Number(6)).value, 13)
+
+
+if __name__ == '__main__':
+    unittest.main()