semvec/pypi-packages huggingface dataset:
zaqwsxcde-test-package 0.0.1
Verilog Domain for Sphinx test Package
Requires Python: >=3.7

sphinx-verilog-domain
=====================

.. warning::

    This extension is in development stage.

Dependencies
------------

* ``lark-parser``

Enabling
--------

Add extension in ``conf.py``::

    extensions = [ 'sphinx_verilog_domain' ]

Usage
-----

Module headers (non-ANSI-style only for now)::

    .. verilog::module:: module Top(a, b);

Port declarations::

    .. verilog:port:: input wire [31:0] a, b;

Parameter declarations::

    .. verilog:parameter:: parameter logic param_name_05 = 1, param_name_05_b = 2;

Custom name for use in references::

    .. verilog:module:: module \35(4p3|) (z);
        :refname: module_escaped

References::

    Reference to :verilog:ref:`Top`
    Reference to :verilog:ref:`module_escaped` - links to ``\\35(4p3|)``

Nesting::

    .. verilog:module:: module Top1(a, b, c);

        .. verilog:port:: input a;

            Description of port ``a``

        .. verilog:port:: input b;

            Description of port ``b``

        .. verilog:module:: module Nested(a);

            .. verilog:port:: output a;

                Description of port ``a`` in ``Nested``

            Reference to module ``Top1``'s port ``a``: :verilog:ref:`Top1.a`.

Namespaces
^^^^^^^^^^

There are three directives for changing current Verilog scope:

* ``.. verilog:namespace:: A::B`` - sets current scope to ``A::B``. Using ``$root`` as an argument or using the directive without argument at all sets global namespace.

* ``.. verilog:namespace-push:: C::D`` - sets current scope to ``C::D`` relatively to current scope

* ``.. verilog:namespace-pop::`` - restores scope which was active before previous ``namespace-push`` was called. If there is no matching ``namespace-push``, scope is set to global scope.

.. note::
    ``verilog::namespace`` resets push/pop stack

Example::

    .. verilog:namespace:: A::B
    .. verilog:port:: input inside_a_b;
    .. verilog:namespace-push:: C::D
    .. verilog:port:: input inside_a_b_c_d;
    .. verilog:namespace-pop::
    .. verilog:port:: input inside_a_b_again;
    .. verilog:namespace::
    .. verilog:port:: input in_global_namespace;

Development
-----------

To create and open the development environment with all system
and python packages use::

   make env
   source env/conda/bin/activate sphinx-verilog-domain
awsunusedresources 0.1.6
A package for identifying unused resources in aws
Requires Python: >=3.7.0

## Un-used AWS Resources

To identify Unused resources in AWS , Just import these package and call the `unused_res` with the following parameters

    ```python
    unused_res("12", "xyz@gmail.com",
               "zyx@gmail.com", "SAP", "sbx")
    ```           

# Days 
    From How long these resources has not been used. For example , If we provide days as `14`, Start date will be today date -14 , end date will be today's date.

# Sender
    We have used SES to send the formatted mail(html), so it is the Mail Id from where it need to send.

# Receiver
    Receiver Mail Id

# App
    For sending the subject in mail , we need these application information. Ex: SAP, ACE etc..,

# Env
    Against which environment is running these code. Ex: SBX, DEV,INT etc..,

# As of now , the following resources can be identified as unused(`Based on CPU Utilization , Invocation/request count etc..,`) if they didn't used for the specified number of days.

`AWS::EC2::Volume`
`AWS::EC2::EIP` 
`AWS::Elasticsearch::Domain`
`AWS::ECS::Service`
`AWS::EC2::SecurityGroup` 
`AWS::EC2::Instance`
`AWS::EC2::NatGateway`
`AWS::ElasticLoadBalancingV2::LoadBalancer` 
`AWS::ACM::Certificate`
`AWS::RDS::DBCluster`
`AWS::S3::Bucket` 
`AWS::DynamoDB::Table`
`AWS::CodeBuild::Project`
`AWS::Lambda::Function` 
`AWS::ApiGateway::RestApi`
`AWS::ApiGatewayV2::Api`
`AWS::CodePipeline::Pipeline` 
`AWS::SQS::Queue`
`AWS::SNS::Topic`
`AWS::SecretsManager::Secret` 
`AWS::Logs::LogGroup`

Many more will be added in the future

# Note:

To Package these file we need `WSL` or `Linux System/container` . 

Few  issues which I faced during packaging : https://github.com/numpy/numpy/issues/13465
django-detect 1.0.20
Django UserAgent Detect
Keywords: django-detect

=============
django-detect
=============

Installation
============

::

    pip install django-detect


Usage
=====

::

    # ####### Device、OS #######
    # Windows
    request.Windows
    # Linux
    request.Linux
    # iMac/iPhone/iPad/iPod
    request.iMac
    request.iPhone
    request.iPad
    request.iPod
    # PC
    request.PC = request.Windows or request.Linux or request.iMac
    # iOS
    request.iOS = request.iPhone or request.iPad or request.iMac or request.iPod
    # Android and Version
    request.Android
    request.Android.version

    # ####### APP #######
    # Weixin／Wechat and Version
    request.weixin
    request.weixin.version
    request.wechat
    request.wechat.version


Settings.py
===========

::

    # Use `MIDDLEWARE_CLASSES` prior to Django 1.10
    MIDDLEWARE = (
        ...
        'detect.middleware.UserAgentDetectionMiddleware',
        ...
    )