semvec/pypi-packages huggingface dataset:
ignition-kernel 1.0.0
Jupyter kernel provisioner for connecting to an Ignition instance.
Requires Python: >=3.6.1

# Ignition kernel provisioner
Juptyer kernel provisioner to orchestrate interfacing with Ignition

# Overview

This project allows connections to be added to Jupyter that let it coordinate requesting kernels from an Ignition instance. The Ignition instance requires a project that contains all the needed code; see the sibling repo `ignition-project` for the project export to load.

The provisioner requires at least Python 3.6.1 as per `jupyter-client` >=v7.0.0.


# Quickstart

`pip install ignition_kernel --upgrade`

For a blank, fresh install gateway:
`python -m ignition_kernel --install`

I have a cert just to stay in the habit of using HTTPS, so my setup looks like this:

```sh
c:\Workspace>python -m ignition_kernel --install --hostname https://localhost.corso.systems:8043

Adding the following kernel:
Config                         Value
------------------------------ -----
Name                           Ignition-CS-Surface61
Gateway Homepage               https://localhost.corso.systems:8043
WebDev Endpoint                system/webdev/jupyter/kernel
Auth username                  admin
Password in Keyring            False
Enter the password for the user 'admin' :
Password saved in Keyring for admin@https://localhost.corso.systems:8043

c:\Workspace>
```
google-books-driver 0.0.1
Functions required by the hirmeos-google-books-driver
Requires Python: >=3.10

===================
Google Books Driver
===================

Load csv reports from google books. There are two options:

- Option 1: Input the google credentials and download the report csv 
  requested whithin a date range, it will return a string holding the csv report 
  content.

- Option 2: Process a csv upoloaded by the user with the option of checking 
  the expected headers.


Note: If the option 1 is required it's recommended to use the option 2 afterwars to 
convert the result (string representation of the csv report) to a list of dict.


Troubleshooting
===============

First of all if the scraping with Selenium is needed, 
we have to create a google account only for the purpose of this driver. 
Shuch account has to have a recovery email account to allow the Selenium download 
the report freely.

It is very important to check the output the first time the driver is run as it 
is very likely that Google will block the 'suspicious' login attempt. If it does, 
you will need to login with the same credentials you have provided the driver 
with and review the security settings, Google will ask if you 
were prevented from logging in and you must confirm so. Afterwards 
re-run the driver and it should work just fine.

The alternative to the scraping is uploading the report manually to bypass 
the scraping functionality as it could be unreaiable because of the frontend 
and/or backend changes from google.
hirmeos-google-books-driver 0.1.4
Functions required by the hirmeos-google-books-driver
Requires Python: >=3.10

===================
Google Books Driver
===================

Load csv reports from google books. There are two options:

- Option 1: Input the google credentials and download the report csv 
  requested whithin a date range, it will return a string holding the csv report 
  content.

- Option 2: Process a csv upoloaded by the user with the option of checking 
  the expected headers.


Note: If the option 1 is required it's recommended to use the option 2 afterwars to 
convert the result (string representation of the csv report) to a list of dict.


Troubleshooting
===============

First of all if the scraping with Selenium is needed, 
we have to create a google account only for the purpose of this driver. 
Shuch account has to have a recovery email account to allow the Selenium download 
the report freely.

It is very important to check the output the first time the driver is run as it 
is very likely that Google will block the 'suspicious' login attempt. If it does, 
you will need to login with the same credentials you have provided the driver 
with and review the security settings, Google will ask if you 
were prevented from logging in and you must confirm so. Afterwards 
re-run the driver and it should work just fine.

The alternative to the scraping is uploading the report manually to bypass 
the scraping functionality as it could be unreaiable because of the frontend 
and/or backend changes from google.