semvec/pypi-packages huggingface dataset:
django-notifications-views 0.3.1
Django-notifications-views is an extension for Django-notifications-hq that provides a viewset for the notifications.
License: MIT
Requires Python: >=3.8
Keywords: django notifications hq views


# Django-notifications-views
Django-notifications-views is an extension for Django-notifications-hq that provides a viewset for the notifications and expo notifications.

## Requirements
- Django >= 3.8 *
- Python >= 3.8 *
- django-notifications-hq >= 1.8 *


(*) Not tested with earlier versions.

## Quick Setup

Install package

    pip install django-notifications-views
    
Add `django_notifications_views` app to INSTALLED_APPS in your django settings.py:

```python
INSTALLED_APPS = (
    ...,
    "django.contrib.staticfiles",
    "rest_framework",  # required only if using the provided REST endpoints
    'notifications',
    'django_notifications_views',
     ...,
)
```
    
Include viewset routes

```python
from django_notifications_views.urls import router as django_notifications_views_router
your_router.registry.extend(django_notifications_views_router.registry)
```

Add the following to your settings.py if you want to enable Expo Go notifications:

```python
DJANGO_NOTIFICATIONS_VIEWS = {
    'USE_EXPO_NOTIFICATIONS': True, # Set to True to enable expo notifications
    'EXPO_APP_ID': '<your-expo-app-id>', 
}

Then run the migrations:

    python manage.py makemigrations
    python manage.py migrate


##  Urls

 GET /api/user-notifications/ : Get all notifications for the current user
 POST /api/user-notifications/read-all/ : Mark all notifications as read for the current user
 GET /api/user-notifications/<int:pk>/ : Get a notification by id and mark it as read

 # Expo Notifications
 POST /api/expo-devices/register-device/ : Register a device to receive expo notifications
 POST /api/expo-devices/unregister-device/ : Unregister a device to stop receiving expo notifications


## Contributing

-   [Juan Ignacio Borrelli](https://www.linkedin.com/in/juan-ignacio-borrelli/)
    

Maintained and developed by [Linkchar Software Development](https://linkchar.com/).
xontrib-langenv 1.2.2
Pyenv/Nodenv/Goenv/Rbenv integration for xonsh
License: MIT
Requires Python: <4.0,>=3.8

# xontrib-langenv

[xonsh](https://xon.sh) integration with:

* [Pyenv](https://github.com/pyenv/pyenv)
* [Nodenv](https://github.com/nodenv/nodenv)
* [Goenv](https://github.com/syndbg/goenv)
* [Rbenv](https://github.com/rbenv/rbenv)

This xontrib replaces the slow `langenv` initialization with a faster python version (and skips the `rehash` step), which could save up to ~0.5s for each `lang`

The only two exceptions are:

  - `goenv`, which requires an extra `rehash --only-manage-paths` [init step](https://github.com/syndbg/goenv/blob/e1007619dbb180c8f8032a9dcdb7afbeb88e848a/libexec/goenv-init#L167) to set some more [environment variables](https://github.com/syndbg/goenv/blob/e1007619dbb180c8f8032a9dcdb7afbeb88e848a/libexec/goenv-sh-rehash#L24)
  - `virtualenv-init`

so if you rewrite that `goenv` env var setting and `pyenv` `virtualenv` init logic in python and xontribute to this xontrib, you could eliminate the last sources of xonsh langenv startup delay!

## Install

Install using pip

```
pip install xontrib-langenv
```

## Usage

Add to your `.xonshrc` as follows:

### Pyenv

```sh
xontrib load pyenv
```

This xontrib initializes `pyenv` when `xonsh` is started.
After initialization `pyenv` commands works as they would do in any *classic* shell.

Also supports [pyenv-virtualenv](https://github.com/pyenv/pyenv-virtualenv).

### Nodenv

```sh
xontrib load nodenv
```

This xontrib initializes `nodenv` when `xonsh` is started.
After initialization `nodenv` commands works as they would do in any *classic* shell.

### Goenv

```sh
xontrib load goenv
```

This xontrib initializes `goenv` when `xonsh` is started.
After initialization `goenv` commands works as they would do in any *classic* shell.

### Rbenv

```sh
xontrib load rbenv
```

This xontrib initializes `rbenv` when `xonsh` is started.
After initialization `rbenv` commands works as they would do in any *classic* shell.

## Compatibility notes

If you are using `xonsh` v0.11 (or older) and you have issues with the latest version of this xontrib, try to downgrade it to version 1.0.6.