semvec/pypi-packages huggingface dataset:
gosnmp-traps-python 1.0.0
gosnmp-traps-python
License: MIT

# gosnmp-traps-python

This library binds [our fork](https://github.com/ftpsolutions/gosnmp) of [gosnmp](https://github.com/gosnmp/gosnmp) for use in Python3
using [gopy](https://github.com/go-python/gopy).

## Versions

All versions 1.0.0 and up support Python 3 only! If you need Python 2 support, check out the following:

- [https://github.com/ftpsolutions/gosnmp-traps-python/tree/v0.91](https://github.com/ftpsolutions/gosnmp-traps-python/tree/v0.91)
- https://pypi.org/project/gosnmp-traps-python/0.91/

## Concept

In the early days `gopy` was fairly limited in it's ability to track object allocation across the border of Go and Python.

As a result, our implementation is fairly naive- we only pass primitive types from Go to Python (nothing that comes by reference).

Session are managed entirely on the Go side and identified with an integer- here are a few function signatures to demonstrate:

- `NewRPCSession(hostname string, port, timeout int, paramsJSON string) (uint64, error)`
- `RPCConnect(sessionID uint64) error`
- `RPCGetNoWait(sessionID uint64) (string, error)`
- `RPCClose(sessionID uint64)`

The functions that return complex data do so in a special JSON-based format- at this point `gopy` does it's magic and those functions are
made available to Python.

We then have `RPCSession` abstraction on the Python side that pulls things together in a class for convenience (saving you need the to keep
track of the identifiers and handling deserialisation).

## Weird gotchas

We're building for Python3 and we use a `python-config` script for Python3 however we're using a `python.pc` file from Python2.

I dunno why this has to be this way, but it's the only way I can get the C Python API GIL lock/unlock calls to be available to
Go (`C.PyEval_SaveThread()` and `C.PyEval_RestoreThread(tState)`).

So if you're wondering why Python2 still comes into it here and there- that's why. Doesn't seem to cause any problems.

## Prerequisites

- MacOS
- CPython3.8+
- virtualenv
    - `pip install virtualenv`
- pkgconfig
    - `brew install pkg-config`
- Docker

## Install (from PyPI)

```
python -m pip install gosnmp-traps-python
```

## Setup

```
virtualenv -p $(which python3) venv
source venv/bin/activate
./fix_venv.sh
pip install -r requirements-dev.txt
```

## Build

```
source venv/bin/activate
./native_build.sh
```

If you're deep in the grind and want to iterate faster, you can invoke:

```
./native_build.sh fast
```

This skips the setup (assuming you've already done that).
gossh-python 1.0.0
gossh-python
License: MIT

# gossh-python

This library binds [crypto/ssh](https://pkg.go.dev/golang.org/x/crypto/ssh) for use in Python3
using [gopy](https://github.com/go-python/gopy).

## Versions

All versions 1.0.0 and up support Python 3 only! If you need Python 2 support, check out the following:

- [https://github.com/ftpsolutions/gossh-python/tree/v0.91](https://github.com/ftpsolutions/gossh-python/tree/v0.91)
- https://pypi.org/project/gossh-python/0.91/

## Concept

In the early days `gopy` was fairly limited in it's ability to track object allocation across the border of Go and Python.

As a result, our implementation is fairly naive- we only pass primitive types from Go to Python (nothing that comes by reference).

Session are managed entirely on the Go side and identified with an integer- here are a few function signatures to demonstrate:

- `NewRPCSession(hostname, username, password string, port, timeout int) uint64`
- `RPCConnect(sessionID uint64) error`
- `RPCGetShell(sessionID uint64, terminal string, height, width int) error`
- `RPCRead(sessionID uint64, size int) (string, error)`
- `RPCWrite(sessionID uint64, data string) error`
- `RPCClose(sessionID uint64) error`

The functions that return complex data do so in a special JSON-based format- at this point `gopy` does it's magic and those functions are
made available to Python.

We then have `RPCSession` abstraction on the Python side that pulls things together in a class for convenience (saving you need the to keep
track of the identifiers and handling deserialisation).

## Weird gotchas

We're building for Python3 and we use a `python-config` script for Python3 however we're using a `python.pc` file from Python2.

I dunno why this has to be this way, but it's the only way I can get the C Python API GIL lock/unlock calls to be available to
Go (`C.PyEval_SaveThread()` and `C.PyEval_RestoreThread(tState)`).

So if you're wondering why Python2 still comes into it here and there- that's why. Doesn't seem to cause any problems.

## Prerequisites

- MacOS
- CPython3.8+
- virtualenv
    - `pip install virtualenv`
- pkgconfig
    - `brew install pkg-config`
- Docker

## Install (from PyPI)

```
python -m pip install gossh-python
```

## Setup

```
virtualenv -p $(which python3) venv
source venv/bin/activate
./fix_venv.sh
pip install -r requirements-dev.txt
```

## Build

```
source venv/bin/activate
./native_build.sh
```

If you're deep in the grind and want to iterate faster, you can invoke:

```
./native_build.sh fast
```

This skips the setup (assuming you've already done that).
gosnmp-python 1.0.0
gosnmp-python
License: MIT

# gosnmp-python

This library binds [our fork](https://github.com/ftpsolutions/gosnmp) of [gosnmp](https://github.com/gosnmp/gosnmp) for use in Python3
using [gopy](https://github.com/go-python/gopy).

## Versions

All versions 1.0.0 and up support Python 3 only! If you need Python 2 support, check out the following:

- [https://github.com/ftpsolutions/gosnmp-python/tree/v0.91](https://github.com/ftpsolutions/gosnmp-python/tree/v0.91)
- https://pypi.org/project/gosnmp-python/0.91/

## Concept

In the early days `gopy` was fairly limited in it's ability to track object allocation across the border of Go and Python.

As a result, our implementation is fairly naive- we only pass primitive types from Go to Python (nothing that comes by reference).

Session are managed entirely on the Go side and identified with an integer- here are a few function signatures to demonstrate:

- `NewRPCSessionV2c(hostname string, port int, community string, timeout, retries int) uint64`
- `RPCConnect(sessionID uint64) error`
- `RPCGet(sessionID uint64, oid string) (string, error)`
- `RPCClose(sessionID uint64) error`

The functions that return complex data do so in a special JSON-based format- at this point `gopy` does it's magic and those functions are
made available to Python.

We then have `RPCSession` abstraction on the Python side that pulls things together in a class for convenience (saving you need the to keep
track of the identifiers and handling deserialisation).

## Weird gotchas

We're building for Python3 and we use a `python-config` script for Python3 however we're using a `python.pc` file from Python2.

I dunno why this has to be this way, but it's the only way I can get the C Python API GIL lock/unlock calls to be available to
Go (`C.PyEval_SaveThread()` and `C.PyEval_RestoreThread(tState)`).

So if you're wondering why Python2 still comes into it here and there- that's why. Doesn't seem to cause any problems.

## Prerequisites

- MacOS
- CPython3.8+
- virtualenv
    - `pip install virtualenv`
- pkgconfig
    - `brew install pkg-config`
- Docker

## Install (from PyPI)

```
python -m pip install gosnmp-python
```

## Setup

```
virtualenv -p $(which python3) venv
source venv/bin/activate
./fix_venv.sh
pip install -r requirements-dev.txt
```

## Build

```
source venv/bin/activate
./native_build.sh
```

If you're deep in the grind and want to iterate faster, you can invoke:

```
./native_build.sh fast
```

This skips the setup (assuming you've already done that).
gomssql-python 1.0.0
gomssql-python
License: MIT

# gomssql-python

This library binds [go-mssqldb](https://github.com/denisenkom/go-mssqldb) for use in Python3 using [gopy](https://github.com/go-python/gopy)
.

## Versions

All versions 1.0.0 and up support Python 3 only! If you need Python 2 support, check out the following:

- [https://github.com/ftpsolutions/gomssql-python/tree/v0.91](https://github.com/ftpsolutions/gomssql-python/tree/v0.91)
- https://pypi.org/project/gomssql-python/0.91/

## Concept

In the early days `gopy` was fairly limited in it's ability to track object allocation across the border of Go and Python.

As a result, our implementation is fairly naive- we only pass primitive types from Go to Python (nothing that comes by reference).

Session are managed entirely on the Go side and identified with an integer- here are a few function signatures to demonstrate:

- `NewRPCSession(dataSourceName string) uint64`
- `RPCConnect(sessionID uint64) error`
- `RPCQuery(sessionID uint64, query string) (uint64, error)`
- `RPCFetchAll(sessionID, rowsID uint64) (string, error)`
- `RPCExecute(sessionID uint64, query string) (uint64, error)`
- `RPCGetRowsAffected(sessionID, resultID uint64) (int64, error)`
- `RPCClose(sessionID uint64) error`

The functions that return complex data do so in a special JSON-based format- at this point `gopy` does it's magic and those functions are
made available to Python.

We then have `RPCSession` abstraction on the Python side that pulls things together in a class for convenience (saving you need the to keep
track of the identifiers and handling deserialisation).

## Weird gotchas

We're building for Python3 and we use a `python-config` script for Python3 however we're using a `python.pc` file from Python2.

I dunno why this has to be this way, but it's the only way I can get the C Python API GIL lock/unlock calls to be available to
Go (`C.PyEval_SaveThread()` and `C.PyEval_RestoreThread(tState)`).

So if you're wondering why Python2 still comes into it here and there- that's why. Doesn't seem to cause any problems.

## Prerequisites

- MacOS
- CPython3.8+
- virtualenv
    - `pip install virtualenv`
- pkgconfig
    - `brew install pkg-config`
- Docker

## Install (from PyPI)

```
python -m pip install gomssql-python
```

## Setup

```
virtualenv -p $(which python3) venv
source venv/bin/activate
./fix_venv.sh
pip install -r requirements-dev.txt
```

## Build

```
source venv/bin/activate
./native_build.sh
```

If you're deep in the grind and want to iterate faster, you can invoke:

```
./native_build.sh fast
```

This skips the setup (assuming you've already done that).
django-session-view-mixin 0.1.3
Your project description goes here
License: MIT
Keywords: django-session-view-mixin

=============================
Django Session View Mixin
=============================

.. image:: https://badge.fury.io/py/django-session-view-mixin.svg/?style=flat-square
    :target: https://badge.fury.io/py/django-session-view-mixin

.. image:: https://readthedocs.org/projects/pip/badge/?version=latest&style=flat-square
    :target: https://django-session-view-mixin.readthedocs.io/en/latest/

.. image:: https://img.shields.io/coveralls/github/frankhood/django-session-view-mixin/master?style=flat-square
    :target: https://coveralls.io/github/frankhood/django-session-view-mixin?branch=master
    :alt: Coverage Status

Your project description goes here

Documentation
-------------

The full documentation is at https://django-session-view-mixin.readthedocs.io.

Quickstart
----------

Install Django Session View Mixin::

    pip install django-session-view-mixin

Add it to your `INSTALLED_APPS`:

.. code-block:: python

    INSTALLED_APPS = (
        ...
        'session_view_mixin',
        ...
    )


Features
--------

* TODO

Running Tests
-------------

Does the code actually work?

::

    source <YOURVIRTUALENV>/bin/activate
    (myenv) $ pip install tox
    (myenv) $ tox


Development commands
---------------------

::

    pip install -r requirements_dev.txt
    invoke -l


Credits
-------

Tools used in rendering this package:

*  Cookiecutter_
*  `cookiecutter-djangopackage`_

.. _Cookiecutter: https://github.com/audreyr/cookiecutter
.. _`cookiecutter-djangopackage`: https://github.com/pydanny/cookiecutter-djangopackage




History
-------

0.1.0 (2021-10-19)
++++++++++++++++++

* First release on PyPI.

0.1.1 (2021-10-20)
++++++++++++++++++

* Update github actions.

0.1.2 (2021-10-21)
++++++++++++++++++

* Fix coveralls.

0.1.3 (2021-10-21)
++++++++++++++++++

* Fix readme.