Saravanan666/pypi-org huggingface dataset:
Package: node.ext.xml
node.ext.xmlXML file abstraction based on nodes.Usagewrite me (or read tests)ContributorsRobert Niederreiter <rnix [at] squarewave [dot] at>Changes0.1initialLicenseCopyright (c) 2010-2013, BlueDynamics Alliance, Austria
All rights reserved.Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.Redistributions in binary form must reproduce the above copyright notice, this
list of conditions and the following disclaimer in the documentation and/or
other materials provided with the distribution.Neither the name of the BlueDynamics Alliance nor the names of its
contributors may be used to endorse or promote products derived from this
software without specific prior written permission.THIS SOFTWARE IS PROVIDED BY BlueDynamics AllianceAS ISAND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL BlueDynamics Alliance BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Package: node.ext.zcml
node.ext.zcmlZCML file abstraction based on nodes.Usagewrite me (or read tests)ContributorsRobert Niederreiter <rnix [at] squarewave [dot] at>Changes0.1initialLicenseCopyright (c) 2010-2013, BlueDynamics Alliance, Austria
All rights reserved.Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.Redistributions in binary form must reproduce the above copyright notice, this
list of conditions and the following disclaimer in the documentation and/or
other materials provided with the distribution.Neither the name of the BlueDynamics Alliance nor the names of its
contributors may be used to endorse or promote products derived from this
software without specific prior written permission.THIS SOFTWARE IS PROVIDED BY BlueDynamics AllianceAS ISAND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL BlueDynamics Alliance BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Package: nodefinder
NodeFinderThe goal of this code is to identify nodal features in potential landscapes, using a two-step approach:Search:Starting from a grid of starting points, find an initial set of nodal points by using a minimization scheme (Nelder-Mead). The initial set of nodes can be further refined by searching in their vicinity. This should produce a point cloud which lies densely within the nodal features to be discovered.Identification:Identify the features (points, lines, surfaces) which are contained in the point cloud. For this step, the nodal points are first separated into clusters. For each cluster, the dimension is estimated, and depending on the points are evaluated further.The initial use-case for this code is to find gapless features in three-dimensional materials.Documentation:https://nodefinder.greschd.ch
Package: nodefluxapis
Nodeflux APIsThis repository contains the public Nodeflux Analytics API. It uses Protocol Buffers version 3 to define the API interface and the structure of the payload messages.You can use the Nodeflux APIs by using the generated code from this repository. We've also built several client libraries, which are the recommended way to call the Nodeflux APIs:Nodeflux Cloud Client for PythonGenerate Source CoreTo generate language specific source code from this repository, you need to install Protocol Buffer, gRPC, and some language specific plugins in your machine. Then you can usemaketo generate the source code.TL;DRThis guides assume you have all dependencies installed. To install the dependencies, see language specific guides below.git clone https://github.com/googleapis/googleapis.git
export GOOGLEAPIS_PATH=$(pwd)/googleapis

make all                                      # Run linter and build all
make CPP_OUT_DIR=/path/to/genfiles cpp        # Build c++ sources
make PYTHON_OUT_DIR=/path/to/genfiles python  # Build python sources
make GO_OUT_DIR=/path/to/genfiles go          # Build go sources
make docs                                     # Build documentation
make lint                                     # Run linterC++To build the C++ source codes, you need to have the following dependencies:Protocol Buffer(Installation Guide)gRPC Plugin for C++ (Installation Guide)googleapisBuild the source code by running the following commands:git clone https://github.com/googleapis/googleapis.git
export GOOGLEAPIS_PATH=$(pwd)/googleapis

make CPP_OUT_DIR=/path/to/genfiles cppPythonTo build the Python source codes, you need to have the following dependencies:Protocol BuffergRPC Plugin for Pythonmypy-protobufgoogleapisThe dependencies above can be installed by running the following commands:pip3 install grpcio-tools mypy-protobuf

git clone https://github.com/googleapis/googleapis.git
export GOOGLEAPIS_PATH=$(pwd)/googleapisThen you can build python source codes:Then you can build and install python source codes:make python
pip install .If you want to build the python sources to different directory, use thePYTHON_OUT_DIRargument.make PYTHON_OUT_DIR=/path/to/genfiles pythonGoTo build the Python source codes, you need to have the following dependencies:Protocol Buffer(Installation Guide)Protocol Buffer for GolanggRPC Plugin for GogoogleapisThe dependencies above can be installed by running the following commands:go get -u github.com/golang/protobuf/protoc-gen-go
go get -u google.golang.org/grpc

git clone https://github.com/googleapis/googleapis.git
export GOOGLEAPIS_PATH=$(pwd)/googleapisThen you can build go source codes:make GO_OUT_DIR=/path/to/genfiles go
Package: node-graph
NodeGraphA platform for designing node-based workflows.pip install --upgrade --user node_graphDocumentationCheck thedocsand learn about the features.ExamplesA simple math calculationfromnode_graphimportNodeGraphnt=NodeGraph(name="example")float1=nt.nodes.new("Float",value=2.0)float2=nt.nodes.new("Float",value=3.0)add1=nt.nodes.new("Operator",operator="+")nt.links.new(float1.outputs[0],add1.inputs[0])nt.links.new(float2.outputs[0],add1.inputs[1])ntdata=nt.to_dict()LicenseMIT
Package: nodejs-eval
NodeJS EvalEvaluate arbitrary JavaScript from Python, using a NodeJS sidecar process.This combines:The Pythonnodejs-binproject, which
bundles NodeJS (withnpmandnpx) into a PyPI package, andThe JavaScript/TypeScripthttp-evalproject, which runs a
JavaScript evaluation server on a Unix domain socket.Table of ContentsInstallationLicenseUsage instructionsInstallationpip install nodejs-evalLicensenodejs-evalis distributed under the terms of theMITlicense.Usage instructionsBasic synchronous callJavaScript code is evaluated as a function body within a synchronous or
asynchronous JavaScript function, within an ECMAScript module.Note that the NodeJS evaluator always only supportsasyncmode on the Python
side. However, the supplied JavaScript code can be either sync or async.fromnodejs_evalimportevaluatorasyncwithevaluator()ase:result=awaite.run("return 6*7;")assertresult==42Basic asynchronous callfromnodejs_evalimportevaluatorasyncwithevaluator()ase:result=awaite.run_async("""await new Promise(r => setTimeout(r, 2000));return 6*7;""")assertresult==42Storing state onthisEvaluations run with a consistent JavaScriptthiscontext, so state can be
stored on it:fromnodejs_evalimportevaluatorasyncwithevaluator()ase:awaite.run("this.x = 6*7;")result=awaite.run("return this.x;")assertresult==42Import using dynamicawait import()Because code is executed within an ECMAScript module, you can usethe dynamic asyncimport()to import other modules.This is easiest done inasyncmode:fromnodejs_evalimportevaluatorasyncwithevaluator()ase:result=awaite.run_async("""const os = await import("os");return os.cpus();""")assertlen(result)>0
Package: nodejs-porter
# nodejsporter#### Description
A rpm packager bot for  nodejsmodules from npmjs.org
It is a tool to create spec file and create rpm for nodejs modules.#### Installationpython3 setup.py install#### Preparation
yum install below software before using this tool
1.  gcc
2.  gdb
3.  libstdc++-devel
4.  python3-cffi
5.  nodejsrpm -ivh nodejs-packaging-23-1.noarch.rpm of this url:https://gitee.com/chendong1995/nodejs-packaging?_from=gitee_search#### Instructionsnodejsporter is a tool to create spec file and create rpm for  nodejsmodules
For more details, please use nodejsporter -hnodejsporter <package> -s -b -d -o  nodejs-<package>.spec#### ContributionFork the repositoryCreate Feat_xxx branchCommit your codeCreate Pull Request#### How to create a rpm fileCreate spec file, nodejsporter -s module_nameGet required  nodejsmodules, nodejsporter -R module_nameBuild and Install rpm package, nodejsporter -B module_namespecify version , nodejsporter -B module_name 1.0.0For more detail, nodejsporter -h
Package: nodejs-wheel
Unoffical Node.js wheelsnodejs-wheelis an unofficial repository to distribute Node.js prebuilt wheels through PyPI usingpipinstallnodejs-wheelThe package requires Python 3.7 and above.The project is powered byscikit-build-coreandcibuildwheel.Available BuildsOSArchBitConditionsLinuxx86_6464glibc >= 2.17macOSx86_6464>= macOS-10.9macOSarm6464>= macOS-11Windowsamd6464Usagenode-h
npm-h
npx-hLicensenodejs-wheeldistributed under the same MITlicenseasNode.js.Other projectsThe project is inspired by many other similiar projects:samwillis/nodejs-pypi: The package redistribute the official Node.js binaraies to PyPI. However, the offical binary for Nodejs 18 requires GLIBC 2.28, making it unsupported inmanylinux2014images. Besides, the wheel tag is wrong.sbwml/node-latest-centos: Use GitHub Actions to build Node.js in CentOS 7, but is not related to Python or PyPI.scikit-build/cmake-python-distributions: Use cibuildwheel and scikit-build to build CMake and distribute CMake in PyPI.
Package: nodemaster
nodemasterintroductionThis module provides various utilities that can be used for the control
and diagnostics of a set of computing nodes. It could be used to check
if a set of computers are accessible via SSH or could run a command on a
set of computers accessible via SSH, for examples.launch commands in tmuxCommands can be sent to respective panes of tmux. The following example
defines multiple commands, launches tmux, creates multiple panes in tmux
and then runs each command in its respective tmux pane.importnodemastercommands=["ls","ls","ls","ls"]nodemaster.launch_tmux(commands=commands)The following example, for use on LXPLUS, illustrates how nodemaster can
be used to send multiple commands out to multiple nodes and to observe
the output in tmux.importnodemastercommands=["ssh -o StrictHostKeyChecking=no lxplus0000.cern.ch uptime","ssh -o StrictHostKeyChecking=no lxplus0001.cern.ch uptime","ssh -o StrictHostKeyChecking=no lxplus0002.cern.ch uptime","ssh -o StrictHostKeyChecking=no lxplus0003.cern.ch uptime"]nodemaster.launch_tmux(commands=commands)
Package: nodemon-py-simple
nodemon-py-simpleNodemon like for python, very simple and without dependenciesThis script watches a directory for file changes and executes a process when a file is modified or added. The process can also be killed if necessary. Additionally, the script can be configured to only watch files with specific extensions and to clear the console before executing the process.And why this package when nodemon exists? Because I no longer want to install node, npm... just for nodemon on my docker images and I haven't found an alternative in python without dependencies.Installationpip install nodemon-py-simpleUsageTo use this script, use the following command line:python script.py directory [options] commandThe available options are as follows:-e,--extensions: a list of file extensions to watch, separated by commas-k,--kill: the process name of the process to kill when a file is modified or added-m,--modified-time: update modified time of the file (like modd)-c,--clear: clear the console before executing the commandContributingThank you for considering contributing to this project!To contribute, please follow these steps:Fork the repositoryCreate a new branch for your changesMake your changes and commit them to your branchPush your branch to your forked repositoryCreate a pull request to the original repositoryNote: Before creating a pull request, please make sure that your changes are consistent with the overall code style and structure of the project. Thank you for your contribution!
Package: nodens-gateway
The purpose of this program - NodeNs Gateway - is to operate an MQTT gateway for connection to NodeNs sensors. The gateway will detect NodeNs sensors connected to the MQTT host, process their data, and optionally publish to a Cloud service and/or save to local storage.InstallationNodeNs Gateway can be installed using pip:pip install nodens.gatewayTroubleshootingInstalling PyYaml. Pip sometimes has trouble installing the PyYaml package. If you experience this, it may be easier to install it manually:pip install pyyamlOperationNodeNs Gateway can be executed directly from the command line as follows:python -m nodens.gatewayIt can also be imported as a library into your own scripts:import nodens.gatewayOn execution, as a first step it will search for the configuration fileconfig-gateway.yamlto define the MQTT broker and other basic settings. The program will first search for the config file in the User's (your) default config folder, and then in the folder you've executed the program from. If the config file is not found, it will create one based on a default configuration.Click here for details of the Configuration.If a Cloud service operation has been specified, the script will also search for relevant access tokens or certificates.ConfigurationLocation of configuration fileThe program will search for the configuration fileconfig-gateway.yamlin the following order:In the user config folder, e.g.Windows:/Users/<user>/AppData/Local/NodeNs/Gateway/Unix:~/.config/Gateway/In the current working folder.In/NodeNs/In/Otherwise, a default config file will be created in the user folder, and the program will print its location. Feel free to edit it as necessary!Description of settingsProgramWRITE_FLAG: Set to1if you require sensor data to be saved to disk. Data will be saved in csv form to:<current folder>/Saved/CLOUD_WRITE_TIME: How often data is saved to a Cloud service (if activated)SensorSensor_IP: IP address of the MQTT broker.Default: 10.3.141.1.Thingsboard setupThingsboard provisioning:https://thingsboard.io/docs/paas/getting-started-guides/helloworld/#step-1-provision-device
Package: nodens-update
The purpose of this program - NodeNs Update - is to update a NodeNs sensor configuration via the MQTT gateway. The new configuration will be defined through the file:config-gateway.yaml.Change logv24.2.0. Added custom radar calibrations to the configuration update, usingRADAR_CAL.InstallationNodeNs Update can be installed using pip:pip install nodens.updateTroubleshootingInstalling PyYaml. Pip sometimes has trouble installing the PyYaml package. If you experience this, it may be easier to install it manually:pip install pyyamlOperationNodeNs Update can be executed directly from the command line as follows:python -m nodens.updateIt can also be imported as a library into your own scripts:import nodens.updateOn execution, as a first step it will search for the configuration fileconfig-update.yamlto define the MQTT broker and other basic settings. The program will first search for the config file in the User's (your) default config folder, and then in the folder you've executed the program from. If the config file is not found, it will create one based on a default configuration.Click here for details of the Configuration.If a Cloud service operation has been specified, the script will also search for relevant access tokens or certificates.ConfigurationLocation of configuration fileThe program will search for the configuration fileconfig-gateway.yamlin the following order:In the user config folder, e.g.Windows:/Users/<user>/AppData/Local/NodeNs/Gateway/Unix:~/.config/Gateway/In the current working folder.In/NodeNs/In/Otherwise, a default config file will be created in the user folder, and the program will print its location. Feel free to edit it as necessary!Description of settingsSENSORROOT_ID: MAC address of the root sensor.SENSOR_ID: MAC address of the sensor to be updated.SENSOR_IP: IP address of the MQTT broker. Default = 10.3.141.1SENSOR_PORT: Port. 1883 : unsecured. 8883: secured (security keys must be provided).DATA_TRANSMITTRANSMIT_TIME: How often sensor data is sent via Wi-Fi, in seconds. Default = 2.FULL_DATA_FLAG: Flag to capture full-data for diagnostics. Set to 1 to transmit full diagnostics data via Wi-Fi, such as point clouds and micro-Dopplers. Default = 0.FULL_DATA_TIME: Seconds between full-data captures (must be a multiple of TRANSMIT_TIME). Default = 2.RADARRADAR_SEND_FLAG: Flag to send new radar configuration. Set to 1 to update the radar configuration. Default = 0.ROOM_X_MIN/ROOM_X_MAX: Monitoring size of area (room or virtual zone) to scan. -X/+X is to the left/right respectively, in meters, from the point-of-view of the sensor. The origin is at (0,0,0).ROOM_Y_MIN/ROOM_Y_MAX: As above. By default, sensor points along Y-axis. +Y is looking forward, from the point-of-view of the sensor.Y must be +ve. The origin is at (0,0,0).ROOM_Z_MIN/ROOM_Z_MAX: As above. Z-axis is room height. -Z/+Z is to the down/up respectively, in meters, from the point-of-view of the sensor. The origin is at (0,0,0).
Package: nodeocc
Slurm NodeOCCTUI application for viewing the status of GPU allocations on a Slurm clusterContents:model/: folder containing the fundamental classes definitions to model the Slurm cluster, its jobs and their portions;readers/: folder containing the functions to parse Slurm infrastructure and jobs status from standard unix commands;view/slurm_list.py: a simple list-based viewer of queued and allocated jobs;view/slurm_viz.py: a graphic-based viewer of allocated jobs across Slurm topology;controller/controller.py: the main entrypoint for the curses-based interactive TUI application.Run it with:python controller/controller.pyRequirements: pandas, pycurses.
Package: nodepasta
NodePastaWant to implement a visual scripting system into your program but don't want to write it yourself? NodePasta has got you covered.NodePasta is a node based-visual scripting framework that lets you define your own nodes and it will take care of the rest.
A NodePasta NodeGraph is UI agnostic, meaning you can load and run graphs without needing a UI implented, but the real magic comes from letting your users
develop their own graphs. NodePasta comes pre-packaged with a editor UI written for TKInter, that you can embed into your application.TODOPort Default/Const ValuesSubgraph nodesVariable length inputsDocumentationNode Developer DocsUI Developer DocsTK UI TutorialsStretch GoalsTKForked LinksLive Graph ExecutionAllow Key rebindsColor configurationsGrab multiple nodes to move
Package: nodepool
Nodepool is a system for managing test node resources. It supports launching
single-use test nodes from cloud providers as well as managing access to
pre-defined pre-existing nodes. Nodepool is part of a suite of tools that form
a comprehensive test system, including Zuul.The latest documentation for Nodepool is published at:https://zuul-ci.org/docs/nodepool/The latest documentation for Zuul is published at:https://zuul-ci.org/docs/zuul/Getting HelpThere are two Zuul-related mailing lists:zuul-announceA low-traffic announcement-only list to which every Zuul operator or
power-user should subscribe.zuul-discussGeneral discussion about Zuul, including questions about how to use
it, and future development.You will also find Zuul developers in the#zuulchannel on Freenode
IRC.ContributingTo browse the latest code, see:https://opendev.org/zuul/nodepoolTo clone the latest code, usegit clone https://opendev.org/zuul/nodepoolBugs are handled at:https://storyboard.openstack.org/#!/project/zuul/nodepoolCode reviews are handled by gerrit athttps://review.opendev.orgAfter creating a Gerrit account, usegit reviewto submit patches.
Example:# Do your commits
$ git review
# Enter your username if promptedJoin#zuulon Freenode to discuss development or usage.LicenseNodepool is free software, licensed under the Apache License, version 2.0.Python Version SupportNodepool requires Python 3. It does not support Python 2.
Package: nodered.py
NodeRED.pymake python function to Node-RED node🎛️ requirementsnode.js 18.16.1 or higher(latest stable)nodered.py 0.2.6 or higher, automatically download from internet if no node.js installedpython 3.7 or highertested onOSTestedPassMac 13(Ventura)✅✅Windows 10✅✅Linux(WSL)🚫🌐 install- using pippython-mpipinstallnodered.py- using git(dev)python-mpipinstallgit+https://github.com/oyajiDev/NodeRED.py.git🛠 usageNode-RED initializefromnoderedpyimportREDBuilder,RED,Auth# using builderred=REDBuilder()\.set_user_dir("{user_dir}")\.set_node_red_dir("{node_red_dir}")\.set_admin_root("{admin_root}")\.set_node_root("{node_root}")\.set_port(port)\.set_default_flow("{default_flow}")\.set_remote_access(remote_access)\.set_default_categories([{default_categories}])\.build()# using RED directlyred=RED("{user_dir}","{node_red_dir}","{admin_root}","{node_root}",port,"{default_flow}",remote_access,[{default_categories}])# change editor theme settingsred.editor_theme.palette.editable=Falsered.editor_theme.projects.enabled=False# add authsred.node_auths.append(Auth(username="node-red-py",password="p@ssword"))register Noderegister as decoratorSeenoredpy.decorator.register functionfor detailsfromnoderedpyimportNodefromnoderedpy.decoratorimportregister@register("test")deftest(node:Node,props:dict,msg:dict)->dict:# user codes herereturnmsgregister from Node-RED objectSeenoredpy.decorator.register functionfor detailsapi=API()red.register("test",api.test)Seenoderedpy._propertyfor details of "Property"Seeexamplefor details.register routeroute(get, post)register as decoratorfromnoderedpy.decoratorimportroute# get@route("{route_url}","get")defroute1(params:dict)->dict:return{}# post@route("{route_url}","post")defroute1(datas:dict)->dict:return{}register from Node-RED object# getred.route(lambdaparams:{},"{route_url}","get")# postred.route(lambdadatas:{},"{route_url}","post")staticred.static("/static","{static_directory_or_file_path}")start Node-REDred.start({debug:bool},{callback:MethodType})Todos✅ type support for "list" and "dict"Roadmap To 2.0✅ remove aiohttp server🟩 flexible property ui