Saravanan666/pypi-org huggingface dataset:
Package: c4m-pdk-gf180mcu
This is pre-alpha development of PDKMaster based PDK for open source GF180MCU process.
Proper README still needs to be written.Licensing RationaleOpen source projects and it's surrounding community can only strive when improvements to the
code or application of the code itself are released to the public and allowed to be used by
them. Copyleft type license are using the licensing terms to guarantee this actually happens
and no party uses a 'take-but-don't-give-back' approach. TheGNU Aferro General Public License V3.0is used as main license for
the code in this project as it is a copyleft type license that is also applicable to cloud
services without binary distribution of the code.One of the problems with a strict copyleft license is that it can introduce incompatibilities
with code released under other open source licenses. In order to improve compatibility and
thus also reusablity the code in this repo is multi-licensed. Multi-licensing under
established open source licenses was preferred over custom extension of licenses.TheGNU General Public License V2.0was added as optional license in
order to allow derived code not to be bound by the anti-tivoizationclauses introduced in theGNU General Public License Version 3. The latter was not deemed necessary for this project and the addition was done to increase
compatibility with some corporate policies.TheCERN Open Hardware Licence Version 2 - Strongly Reciprocalis included as it is a copyleft license specifically targeted for hardware but incompatible
with the GPL licenses.TheApache License Version 2.0is included to maximize compatiblity
with existing open source code. One is supposed to not use it to avoid having to release one's
own derived code to the public. If you plan development of a project in a proprietary way, one
is kindly asked to not derive one's code from this project's code.In future the list of allowed licenses may be reduced. A reason could be that such an action
is deemed necessary by the project maintainers to encourage open sourcing of derived code.Analog to how the object files and the executables generated by the gcc compiler are not
necessarily goverened by the GPL license, the multi-licensing applies only to code derived
from code in this repository. Output files generated through the use of the code in this
repository are not by default bound to the multi-licensing requirements of this project's
code.
Package: c4m-pdk-sky130
PDKMaster based Sky130 PDKThis is the PDK for Sky130 based on thePDKMasterframework. It currently is basically undocumented. Development is driven by sky130 MPW shuttle development.
A little more information on what is possible can be found in the.gitlab-ci.ymlfile.Release historyv0.1.5: Update bandgap model support, update analog python notebooks.v0.1.4: No code changes; update dependencies for latest bug fixesv0.1.3: No code change; use PDKMaster 0.9.2 to get Coriolis export compatible with namespace of
latest Coriolis release.v0.1.2: Fix Coriolis export.v0.1.1: No code change; release files now built by CI.v0.1.0: Update forrelease v0.9.0 of PDKMasterno notes for older releases
Package: c4m-PySpice
This is a fork ofPySpice. The purpose of this fork is to be able to publish a package on PyPi with extra changes without conflicting with the upstream project.Patches added to this release:#249: Changes to make it easier to use PySpice with a large archive of SPICE models#256: Support for .nodeset type initial condition.#258: Added spice library support#271: PWL support improvements#272: Add DC temperature sweep support.In order to be able to coexist with upstream PySpice release, the PySpice module has been moved into the c4m namespace. So where one used thePySpicemodule in their code before, one has to now usec4m.PySpiceto access code of this fork. For all other project resources like docs, examples etc. devert to theupstream projectOnly minimal testing has been done on this fork to verify functionality as used byPDKMasteris working properly.
Package: c4v-py
c4v-pySolving Venezuela pressing matters one commmit at a timec4v-pyis a library used to address Venezuela's pressing issues
using computer and data science. Check theonline documentationInstallationDevelopmentPendingInstallationUse pip to install the package:pipinstallc4v-pyUsageTODOCan you help us? Open a new issue in
minutes!ContributingThe following tools are used in this project:Poetryis used as package manager.Noxis used as automation tool, mainly for testing.Blackis the mandatory formatter tool.PyEnvis recommended as a tool to handle multiple python versions in your machine.The library is intended to be compatible with python ~3.6.9, ~3.7.4 and ~3.8.2. But the primary version to support is ~3.8.2.The general structure of the project is trying to follow the recommendations
inCookiecutter Data Science.
The main difference lies in the source code itself which is not constraint to data science code.SetupInstall pyenv and select a version, ie: 3.8.2. Once installed runpyenv install 3.8.2Install poetry in your systemClone this repo in a desired locationgit clone https://github.com/code-for-venezuela/c4v-py.gitNavigate to the foldercd c4v-pyMake sure your poetry picks up the right version of python by runningpyenv local 3.8.2, if 3.8.2 is your right version.Since our toml file is already created, we need to get all dependencies by runningpoetry install. This step might take a few minutes to complete.Install noxFromc4v-pydirectory, on your terminal, run the commandnox -s teststo make sure all the tests run.If you were able to follow every step with no error, you are ready to start contributing. Otherwise,open a new issue!RoadmapAdd CONTRIBUTING guidelinesAdd issue templatesDocument where to find things (datasets, more info, etc.)This might be done (in conjunction) with Github Projects. Managing tasks there might be a good idea.Add LICENSEChange the authors field in pyproject.tomlChange the repository field in pyproject.tomlMove the content below to a place near to the data in the data folder or use the reference folder.
CheckCookiecutter Data Sciencefor details.Understand what is in the following folders and decide what to do with them.brat-v1.3_Crunchy_Frogcreating_modelsdata/data_to_annotatedata_analysisSet symbolic links betweenbrat-v1.3_Crunchy_Frog/dataanddata/data_to_annotate.data_samplerextracts todata/data_to_annotate. Files placed here are read by Brat.Download Brat -wget https://brat.nlplab.org/index.htmluntar brat -tar -xzvf brat-v1.3_Crunchy_Frog.tar.gzinstall brat -cd brat-v1.3_Crunchy_Frog && ./install.shreplace default annotation conf for current configuration -wget https://raw.githubusercontent.com/dieko95/c4v-py/master/brat-v1.3_Crunchy_Frog/annotation.conf -O annotation.confreplace default config.py for current configuration -wget https://raw.githubusercontent.com/dieko95/c4v-py/master/brat-v1.3_Crunchy_Frog/config.py -O config.py
Package: c6
c6 (Circular Center-based Cell Colony Creation and Clustering)C6 is a toy center-based model of the initial clustering that occurs as a cells aggregate after replating.FeaturesRepresents cells as non-overlapping circlesCells exclude each otherCells sense each other with tunable strength and distancesCells grow at tunable ratesCells divide at tunable sizesCells' growth is contact inhibitedRuns are launched from stored initial conditionsRuns are selectable as deterministic or stochasticRuns are logged to tidy data fileRun state is visualizedYou can save run states out to pretty MP4sSummary statistics are available for probing run logsEasy run profilingQuick Startimportc6importnumpyasnpimportmatplotlib.pyplotaspltspace=c6.Space()cell_locs=20*np.random.random((10,2))cells=[c6.Cell(space,loc)forlocincell_locs]fig,ax=plt.subplots(1,1,figsize=(10,10))ax.set(xlim=(-10,20),ylim=(-10,20))animation=c6.plot.animate(fig,ax,space,500)animation.save('example.mp4',fps=20)InstallationClone and install orpip install git+https://github.com/AllenCellModeling/c6.gitCreating initial conditions and logging runsBoth initial conditions and run logs are stored as JSON in this form:{"seed":123,"universal":{"sensing":12.3,"influence_max":12,"influence_decay":0.3,"adhesion":0.5},"cells":[{"time":0,"id":[0,1,...,100],"loc":[[1,2],[3,4],...,[0.5,2]],"radius":[0.3,0.5,...,2.0]}]}Any property that can be passed toc6.Cellas a parameter can be serialized either as a key/value pair in'universal', in which case it applies to all cells at all time points, or to"cells", in which case it is parsed on a per cell per time point basis. Starting conditions are this file, but with only the first entry in"cells"specified. The first entry in"cells"is always applied before later entries and so per-cell values that do not change (e.g. ids) can be set there.DocumentationFor full package documentation please visitAllenCellModeling.github.io/c6.Available under the Allen Institute Software License
Package: c64
c64Experimental package of ASGI utilities extracted from DatasetteThis library is anexperimental alpha. I have not yet committed to maintaining this in the long-term, so you should not use this for any projects.InstallationInstall this library usingpip:$ pip install c64UsageThe library providesRequestandResponseclasses, which currently match the documented classes of the same name in Datasette, seeDatasette internals documentation.DevelopmentTo contribute to this library, first checkout the code. Then create a new virtual environment:cd c64
python -mvenv venv
source venv/bin/activateOr if you are usingpipenv:pipenv shellNow install the dependencies and tests:pip install -e '.[test]'To run the tests:pytest
Package: c64os-util
C64 OS UtilitiesThec64os_utilPython package provides a collection of classes, methods, and
scripts that allow you to parse, generate, or manipulate certain types of files
that are used in C64 OS. This package is useful to developers who are
cross-assembling C64 OS applications and wish to package up their resources as
part of the build pipeline.For installation and usage instructions, or for an overview of features, please
refer to thedocumentation.
Package: c64tools
c64toolsc64toolsis aPythonlibrary that helps in dealing with Commodore c64 graphics and memory.You may find more information athttp://www.krajzewicz.de/docs/c64tools/index.html.The major module is named “c64tools.py”. It contains classes that represent major c64 artifacts — memory, bitmap, char, screen, etc. These classes usually support loading, drawing, and being extracted from a pygame surface.In addition, you may find some applications which use this module:acharpackerac64 memory dump to png rendereracharset from memory dump extractoralinking toolDownload and InstallationThecurrent versionisc64tools-0.18.0.You mayinstall c64toolsusingpython -m pip install c64toolsYou maydownload a copy or fork the codeatc64tools's github page.Besides, you maydownload the current releasehere:c64tools-0.18.0.zipc64tools-0.18.0.tar.gzLinksA complete documentation is located at:https://c64tools.readthedocs.io/en/latest/andhttps://krajzewicz.de/docs/c64tools/index.htmlDiscussions are open athttps://github.com/dkrajzew/c64tools/discussionsThe github repository is located at:https://github.com/dkrajzew/c64toolsThe issue tracker is located at:https://github.com/dkrajzew/c64tools/issuesThe PyPI page is located at:https://pypi.org/project/c64tools/NoteLet me know if you need any further information or advice. I am not actively developingc64toolscurrently.
Package: c65beka
Beka is a fairly basic BGP speaker. It can send
and receive unicast route updates in IPv4 and IPv6,
but not too much else. It is designed to be simple to use
and to extend, without too much overhead.It uses eventlet for concurrency, but is easy enough to port to
gevent if that takes your fancy.More information athttps://github.com/c65sdn/beka
Package: c65ryu
What’s RyuRyu is a component-based software defined networking framework.Ryu provides software components with well defined API’s that make it
easy for developers to create new network management and control
applications. Ryu supports various protocols for managing network
devices, such as OpenFlow, Netconf, OF-config, etc. About OpenFlow,
Ryu supports fully 1.0, 1.2, 1.3, 1.4, 1.5 and Nicira Extensions.All of the code is freely available under the Apache 2.0 license. Ryu
is fully written in Python.Quick StartInstalling Ryu is quite easy:% pip install ryuIf you prefer to install Ryu from the source code:% git clone https://github.com/faucetsdn/ryu.git
% cd ryu; pip install .If you want to write your Ryu application, have a look atWriting ryu applicationdocument.
After writing your application, just type:% ryu-manager yourapp.pyOptional RequirementsSome functions of ryu require extra packages:OF-Config requires lxml and ncclientNETCONF requires paramikoBGP speaker (SSH console) requires paramikoZebra protocol service (database) requires SQLAlchemyIf you want to use these functions, please install the requirements:% pip install -r tools/optional-requiresPlease refer to tools/optional-requires for details.PrerequisitesIf you got some error messages at the installation stage, please confirm
dependencies for building the required Python packages.On Ubuntu(16.04 LTS or later):% apt install gcc python-dev libffi-dev libssl-dev libxml2-dev libxslt1-dev zlib1g-devSupportRyu Official site ishttps://ryu-sdn.org/.If you have any
questions, suggestions, and patches, the mailing list is available atryu-devel ML.The ML archive at Gmaneis also available.
Package: c7n-autodoc
Automated Cloud Custodian Policy DocumentationWhat is c7n-autodoc?Automated Cloud Custodian policy documentation for your business partners.Why use c7n-autodoc?Administrators of cloud platforms need provide their business partners
with clear and accurate documentation regarding the security, governance and
cost control policies.  The easiest way to stay on top of your documentation
is to automate it.  This utility will create an HTML file with easy to read information
regarding your existing Cloud Custodian policies.Features include:Automatically writes to S3 bucketGroups policies by resource typeGroups policies by category (i.e 'Security & Governance' vs 'Cost Controls')Provide links to underlying file in GitLab/GitHubUses policy tags to determine applicable environmentsAssumptionsYou have added any necessary security controls to the destination S3 bucketLocal credentials exist for the boto3 module to push the file to S3InstallationNOTE: Requires python3pip3 install pyyaml boto3 jinja2 jsonschemaConfigurationThe only item you should need to customize is the configuration YAML file which is required by the
script.  Look at the example file provided to determine which fields are required and which
are optional.  You can also customize the jinja2 template to further modify the HTML
documentation which is created.The S3 bucket which will house the HTML file needs to haveStatic website hostingenabled.  The
default (index.html, error.html) are fine because you will be directly targeting the c7n-autodoc.html
file.RunFor the best results this script should be run as a part of a CI/CD pipeline.python3 c7n-autodoc.py -c my_config_file.ymlAssuming there aren't any issues you should see the HTML file in the S3 bucket.ExampleTODOAccount for different policies for proper renderingImproved UI layoutEasier user setup
Package: c7n-azure
Cloud Custodian - Azure SupportThis a plugin to Cloud Custodian that adds Azure support.Install Cloud Custodian and Azure PluginThe Azure provider must be installed as a separate package in addition to c7n.$ git clone https://github.com/cloud-custodian/cloud-custodian.git
$ virtualenv custodian
$ source custodian/bin/activate
(custodian) $ pip install -e cloud-custodian/.
(custodian) $ pip install -e cloud-custodian/tools/c7n_azure/.Write your first policyA policy specifies the following items:The type of resource to run the policy againstFilters to narrow down the set of resourcesActions to take on the filtered set of resourcesFor this tutorial we will add a tag to all virtual machines with the name "Hello" and the value "World".Create a file namedcustodian.ymlwith this content:policies:
    - name: my-first-policy
      description: |
        Adds a tag to all virtual machines
      resource: azure.vm
      actions:
        - type: tag
          tag: Hello
          value: WorldRun your policyFirst, choose one of the supported authentication mechanisms and either log in to Azure CLI or set
environment variables as documented inAuthentication.custodian run --output-dir=. custodian.ymlIf successful, you should see output similar to the following on the command line2016-12-20 08:35:06,133: custodian.policy:INFO Running policy my-first-policy resource: azure.vm
2016-12-20 08:35:07,514: custodian.policy:INFO policy: my-first-policy resource:azure.vm has count:1 time:1.38
2016-12-20 08:35:08,188: custodian.policy:INFO policy: my-first-policy action: tag: 1 execution_time: 0.67You should also find a newmy-first-policydirectory with a log and other
files (subsequent runs will append to the log by default rather than
overwriting it).LinksGetting StartedExample ScenariosExample Policies
Package: c7n-gcp
Custodian GCP SupportStatus - AlphaFeaturesServerless ✅Api Subscriber ✅Metrics ✅Resource Query ✅Multi Account (c7n-org) ✅Getting Startedvia pippip install c7n_gcpBy default custodian will use credentials associated to the gcloud cli, which will generate
warnings per google.auth (https://github.com/googleapis/google-auth-library-python/issues/292)The recommended authentication form for production usage is to create a service account and
credentials, which will be picked up via by the custodian cli via setting theGOOGLE_APPLICATION_CREDENTIALSenvironment variable.ServerlessCustodian supports both periodic and api call events for serverless
policy execution.GCP Cloud Functions require cloudbuild api be enabled on the project
the functions are deployed to.Periodic execution mode also requires cloudscheduler api be enabled on
a project. Cloudscheduler usage also requires an app engine instance
in the same region as the function deployment.
Package: c7n-guardian
c7n-guardian: Automated multi-account Guard Duty setupAmazon Guard Duty provides for machine learning based threat
intelligence and detection on resources in your aws accounts. This
project provides a cli tool for automating multi-account of aws guard
duty. Given a config file holding a set of account information, this
cli will setup one as a master account, and the remainder as member
accounts.The following cli will enable guard duty on all accounts tagged
dev. The master guard duty account can be specified by name or account
id. Running enable multiple times will idempotently converge.$c7n-guardianenable--configaccounts.yml--master120312301231--tagsdevThe accounts config file is similiar to c7n-org, with the addition of the
account email.$cataccounts.yml

accounts:-name:guard-duty-masteremail:guard-duty-master@example.comaccount_id:"2020202020202"role:"arn:aws:iam::2020202020202:role/CustodianGuardDuty"tags:-prod-name:cicdemail:cicd@example.comaccount_id:"1010101010101"role:"arn:aws:iam::1010101010101:role/CustodianGuardDuty"tags:-dev-cicdThe cli also has support for disabling and reporting on accounts$c7n-guardian--help
Usage:c7n-guardian[OPTIONS]COMMAND[ARGS]...AutomateGuardDutySetup.

Options:--helpShowthismessageandexit.

Commands:disablesuspendguarddutyinthegivenaccounts.enableenableguarddutyonasetofaccountsreportreportonguarddutyenablementbyaccountAccounts CredentialsThe cli needs credentials access to assume the roles in the config
file for all accounts (master and members), the execution credentials
used can be sourced from a profile, or from role assumption in
addition to credential sourcing supported by the aws sdk.Using custodian policies for remediationHere's some example policies that will provision a custodian lambda
that receives the guard duty notifications and performs some basic
remediation on the alerted resources, respectively stopping an ec2
instance, and removing an access key. You have the full access to
custodian's actions and filters for doing additional activities in
response to events.policies:-name:ec2-guard-remediateresource:ec2mode:role:arn:aws:iam::{account_id}:role/CustodianPolicyExecutiontype:guard-dutyfilters:# Filter for medium and high severity events-type:eventkey:detail.severityop:gtevalue:4.5actions:-stop-name:iam-guard-remediateresource:iam-usermode:role:arn:aws:iam::{account_id}:role/CustodianPolicyExecutiontype:guard-dutyfilters:# Only a particular type of event, go ahead and remove keys-type:eventkey:detail.typevalue:"UnauthorizedAccess:IAMUser/TorIPCaller"actions:-remove-keys
Package: c7n-kube
Custodian Kubernetes SupportCloud Custodian can run policies directly inside your cluster, reporting on
resources that violate those policies, or blocking them altogether.Running the serverc7n-kates can be run and installed via poetry.poetry install && poetry run c7n-kates.namedefaultdescription--host127.0.0.1(optional) The host that the server should listen on.--port8800(optional) The port the server will listen on.--policy-dirPath to the policy directory.--on-exceptionwarnAction to take on an internal exception. One of: warn, deny.--certPath to the certificate.--ca-certPath to the CA's certificate.--cert-keyPath to the certificate's key.Generate a MutatingWebhookConfigurationAfter the server is running, you'll need to configure and install the
MutatingWebhookConfiguration manually. To generate a webhook configuration, you
can runpoetry run c7n-kates --generate --endpoint $ENDPOINT_URL --policy-dir $DIR, and
it will generate an appropriate configuration for you, based on your policies.Note: some modification of the webhook configuration may be required. See thedocumentationon webhooks for more configuration.DevelopmentYou can useskaffoldto
assist with testing and debugging this controller. Runskaffold devin this
folder to deploy the local container into a local kubernetes cluster. It will
automatically redeploy it as files change.