semvec/pypi-packages huggingface dataset:
nbmask 0.0.5
IPython extension to mask sensitive data
Requires Python: >=3.10
Keywords: ipython, notebook, extension, privacy

# IPython extension to mask sensitive data

Simple ipython extension to mask sensitive data like credentials from notebook cell outputs.
This extensions may be useful to avoid inadvertently displaying sensitive data in public notebooks.
The extension modifies the ipython display system to try and mask any occurence of any of the given strings
that appear in textual outputs from printing, logging and the native display system.

## Usage

To load the extension use the magic command `%load_ext nbmask`. The extension will automatically
mask the notebook display textual outputs without any further magic commands. When first loaded the
extension will mask just the username.

```python
import os
from pathlib import Path

%load_ext nbmask

username = os.getenv('USER')
print("My name is {username}!")
# >>> My name is ...!

documents = Path(f"~/Documents").expanduser()
documents
# >>> PosixPath('/Users/.../Documents')
```


You can add more secrets with the `%nbmask` magic line command
and a string parameter using python builtin variable expansion syntax.


```python
TOKEN = my_secret_token()

%nbmask "$TOKEN"

credentials = dict(user=username, token=TOKEN)

credentials
# >>> {'user': '...', 'token': '...'}
```

The extension modifies standard output, standard error and
also the default logging handlers.

```python
import logging

logging.basicConfig(level="DEBUG")

logging.debug("Token is %s", TOKEN)
# >>> DEBUG:root:Token is ...
```

## Example

See nbmask-tests.ipynb in `extras`

## Installation

You can install the current version of this package with pip

```console
pip install nbmask
```

## Changelog

### 0.05
- Now using `uv_build` backend
- Added testing with `pytest` and `nbmake`
- Requires python >= 3.10 

### 0.0.4
- Cell magic `%%masked` is no longer needed. Will be removed

### 0.0.3
- Masking pattern is cached
ros-trajectory-msgs 5.3.6
ROS trajectory_msgs provides standard messages for defining and communicating robotic joint trajectories for robot control.

Built using https://github.com/ycheng517/ros-python-wheels.

# trajectory_msgs

This package provides several messages for defining robotic joint trajectories.

For more information about ROS 2 interfaces, see [docs.ros.org](https://docs.ros.org/en/rolling/Concepts/About-ROS-Interfaces.html).

## Messages (.msg)
* [JointTrajectory](msg/JointTrajectory.msg): A coordinated sequence of joint configurations to be reached at prescribed time points.
* [JointTrajectoryPoint](msg/JointTrajectoryPoint.msg): A single configuration for multiple joints in a JointTrajectory.
* [MultiDOFJointTrajectory](msg/MultiDOFJointTrajectory.msg): A representation of a multi-dof joint trajectory (each point is a transformation).
* [MultiDOFJointTrajectoryPoint](msg/MultiDOFJointTrajectoryPoint.msg): A single configuration for multiple joints in a MultiDOFJointTrajectory.

## Quality Declaration
This package claims to be in the **Quality Level 2** category, see the [Quality Declaration](QUALITY_DECLARATION.md) for more details.
ros-rcl-lifecycle 9.2.8
ROS 2 `rcl_lifecycle` provides core C functionality for managing lifecycle nodes.

Built using https://github.com/ycheng517/ros-python-wheels.

# rcl_lifecycle

`rcl_lifecycle` provides functionality for ROS 2 lifecycle nodes in C.

Features are described in detail at [http://docs.ros2.org](http://docs.ros2.org/latest/api/rcl_lifecycle/index.html)

For more information about lifecycle nodes, see:
https://design.ros2.org/articles/node_lifecycle.html

## Quality Declaration

This package claims to be in the **Quality Level 1** category, see the [Quality Declaration](./QUALITY_DECLARATION.md) for more details.
ros-rosidl-core-generators 0.2.0
ROS package providing CMake functionality to manage buildtime and runtime dependencies for ROS message and interface packages, reducing boilerplate.

Built using https://github.com/ycheng517/ros-python-wheels.

# rosidl_core_generators

Provides CMake functionality for finding and adding buildtime dependencies for packages providing ROS message definitions.

## Features

The *features* of this package consist entirely of serving as a gathering place for all runtime related dependencies of ROS interface packages.
These dependencies can be found in the [package.xml](package.xml).
This helps reduce the boilerplate needed when developers create their own interface packages.
ros-libyaml-vendor 1.6.3
ROS libyaml_vendor provides a CMake wrapper to ensure the ROS 2 required version of `libyaml` is available, building it if necessary.

Built using https://github.com/ycheng517/ros-python-wheels.

# libyaml_vendor
CMake wrapper to provide libyaml.

The CMake script in this package checks if a `libyaml` that has exactly the version required by ROS 2 is available in the system.

If such `libyaml` is available in the system, it only installs a [`Findyaml.cmake`](cmake/Modules/Findyaml.cmake) CMake find module,
to ensure that the library can be always found via:
~~~cmake
find_package(yaml REQUIRED)
~~~
and linked via:
~~~cmake
target_link_libraries(<target> PRIVATE yaml)
~~~
even if no CMake config file for `yaml` is installed in the system.

If a `libyaml` that has exactly the version required by ROS 2 is not available in the system, then it downloads and installs
`libyaml` as part of this package thanks to [CMake's ExternalProject module](https://cmake.org/cmake/help/latest/module/ExternalProject.html).

The `FORCE_BUILD_VENDOR_PKG` CMake option (that by default is `OFF`) is provided to allow forcing a `libyaml` build, regardless
of what can be found in the system.

## Quality Declaration files

Quality declaration for this package: [libyaml_vendor QD](QUALITY_DECLARATION.md).

Quality declaration of external dependency [libyaml](./libyaml_q_declaration.md).
ros-nav-msgs 5.3.6
ROS nav_msgs package offers standard messages and services for robotic navigation applications.

Built using https://github.com/ycheng517/ros-python-wheels.

# nav_msgs

This package provides several messages and services for robotic navigation.

For more information about the navigation2 stack in ROS 2, see https://ros-planning.github.io/navigation2/.

For more information about ROS 2 interfaces, see [docs.ros.org](https://docs.ros.org/en/rolling/Concepts/About-ROS-Interfaces.html).

## Messages (.msg)
* [GridCells](msg/GridCells.msg): An array of cells in a 2D grid.
* [MapMetaData](msg/MapMetaData.msg): Basic information about the characteristics of the OccupancyGrid.
* [OccupancyGrid](msg/OccupancyGrid.msg): Represents a 2-D grid map, in which each cell represents the probability of occupancy.
* [Odometry](msg/Odometry.msg): This represents an estimate of a position and velocity in free space.
* [Path](msg/Path.msg): An array of poses that represents a Path for a robot to follow.

## Services (.srv)
* [GetMap](srv/GetMap.srv): Get the map as a nav_msgs/OccupancyGrid.
* [GetPlan](srv/GetPlan.srv): Get a plan from the current position to the goal Pose.
* [SetMap](srv/SetMap.srv): Set a new map together with an initial pose.

## Quality Declaration
This package claims to be in the **Quality Level 2** category, see the [Quality Declaration](QUALITY_DECLARATION.md) for more details.
ros-rcl-yaml-param-parser 9.2.8
A ROS 2 package to parse YAML parameter files into C data structures for node initialization.

Built using https://github.com/ycheng517/ros-python-wheels.

# ROS 2 rcl YAML parameter parser

Parse a YAML parameter file and populate the C data structure.

Features are described in detail at [http://docs.ros2.org](http://docs.ros2.org/latest/api/rcl_yaml_param_parser/index.html)

The data structure params_st will then be used during node initialization

YAML parameter file should follow the yaml syntax shown below

NOTE: It only supports canonical int and float types

```
<node_namespace_string>:  # optional
  <node1_name>:
    ros__parameters:
      <field_name>: <field_value>
      <parameter_namespace_string>:   # optional
        <field1_name>: <field1_value>
        <field2_name>: <field2_value>
  <node2_name>:
    ros__parameters:
      <field_name>: <field_value>
      <parameter_namespace_string>:   # optional
        <field1_name>: <field1_value>
        <field2_name>: <field2_value>
```

This package depends on C libyaml.

## Quality Declaration

This package claims to be in the **Quality Level 1** category, see the [Quality Declaration](./QUALITY_DECLARATION.md) for more details.
ros-std-srvs 5.3.6
ROS `std_srvs` provides standard, simple service definitions like Empty, SetBool, and Trigger for common robot functionalities.

Built using https://github.com/ycheng517/ros-python-wheels.

# std_srvs

This package provides several service definitions for standard but simple ROS services.

For more information about ROS 2 interfaces, see [docs.ros.org](https://docs.ros.org/en/rolling/Concepts/About-ROS-Interfaces.html).

## Services (.srv)
* [Empty.srv](srv/Empty.srv): A service containing an empty request and response.
* [SetBool.srv](srv/SetBool.srv): Service to set a boolean state to true or false, for enabling or disabling hardware for example.
* [Trigger.srv](srv/Trigger.srv): Service with an empty request header used for triggering the activation or start of a service.


## Quality Declaration
This package claims to be in the **Quality Level 1** category, see the [Quality Declaration](QUALITY_DECLARATION.md) for more details.
ros-rcpputils 2.11.2
rcpputils is a ROS 2 C++ utility package providing common macros, functions, and data structures for various development needs.

Built using https://github.com/ycheng517/ros-python-wheels.

# rcpputils: ROS 2 C++ Utilities
![License](https://img.shields.io/github/license/ros2/rcpputils)
![Test rcpputils](https://github.com/ros2/rcpputils/workflows/Test%20rcpputils/badge.svg)


`rcpputils` is a C++ API consisting of macros, functions, and data structures intended for use throughout the ROS 2 codebase

## Quality Declaration

This package claims to be in the **Quality Level 1** category, see the [Quality Declaration](QUALITY_DECLARATION.md) for more details.

## API
This package currently contains:
* Assertion functions
* Clang thread safety annotation macros
* Library discovery
* String helpers
* File system helpers
* Type traits helpers
* Class that dynamically loads, unloads and get symbols from shared libraries at run-time.

Features are described in more detail at [docs/FEATURES.md](docs/FEATURES.md)
ros-rcl-action 9.2.8
This ROS 2 package provides Python bindings for the core C functionality of ROS 2 actions.

Built using https://github.com/ycheng517/ros-python-wheels.

# rcl_action

`rcl_action` provides functionality for ROS 2 actions in C.

Features are described in detail at [http://docs.ros2.org](http://docs.ros2.org/latest/api/rcl_action/index.html)

For more information about ROS 2 actions, see:
http://design.ros2.org/articles/actions.html

## Quality Declaration

This package claims to be in the **Quality Level 1** category, see the [Quality Declaration](./QUALITY_DECLARATION.md) for more details.
ros-rosgraph-msgs 2.0.3
rosgraph_msgs is a ROS package defining low-level messages for the ROS Computation Graph, including the Clock message for current ROS time.

Built using https://github.com/ycheng517/ros-python-wheels.

# rosgraph_msgs
This is a package containing message definitions relating to the ROS Computation Graph. These are generally considered to be low-level messages that end users do not interact with.

For more information about ROS 2 clock, see [design.ros2.org](https://design.ros2.org/articles/clock_and_time.html).

For more information about ROS 2 interfaces, see [docs.ros.org](https://docs.ros.org/en/rolling/Concepts/About-ROS-Interfaces.html).

## Messages (.msg)
* [Clock](msg/Clock.msg): Communicates the current ROS time.

## Quality Declaration
This package claims to be in the **Quality Level 1** category, see the [Quality Declaration](QUALITY_DECLARATION.md) for more details.
ros-actionlib-msgs 5.3.6
This deprecated ROS 1 package provides message definitions for bridging ROS 1 action topics.

Built using https://github.com/ycheng517/ros-python-wheels.

This package is **deprecated** and exists to support bridging ROS 1 action topics.
For ROS 2 actions, see [action_msgs](https://github.com/ros2/rcl_interfaces/tree/master/action_msgs).
ros-rosidl-core-runtime 0.2.0
A ROS package providing CMake functionality to manage runtime dependencies for ROS message definition packages, simplifying interface creation.

Built using https://github.com/ycheng517/ros-python-wheels.

# rosidl_core_runtime

Provides CMake functionality for finding and adding runtime dependencies for packages providing ROS message definitions.

## Features

The *features* of this package consist entirely of serving as a gathering place for all runtime related dependencies of ROS interface packages.
These dependencies can be found in the [package.xml](package.xml).
This helps reduce the boilerplate needed when developers create their own ROS interface packages.

## Quality Declaration

This package claims to be in the **Quality Level 1** category, see the [Quality Declaration](QUALITY_DECLARATION.md) for more details.
ros-ament-cmake-gen-version-h 2.5.4
Wheel for the ament_cmake_gen_version_h (ros-ament-cmake-gen-version-h) ROS 2 package.

Wheel for the ament_cmake_gen_version_h (ros-ament-cmake-gen-version-h) ROS 2 package. Built using https://github.com/ycheng517/ros-python-wheels
ros-rmw-fastrtps-shared-cpp 8.4.3
This ROS package provides shared C++ code for static and dynamic type support within the rmw_fastrtps_cpp implementation.

Built using https://github.com/ycheng517/ros-python-wheels.

# `rmw_fastrtps_shared_cpp`

`rmw_fastrtps_shared_cpp` provides common code for static and dynamic type support of rmw_fastrtps_cpp.

## Quality Declaration

This package claims to be in the **Quality Level 2** category, see the [Quality Declaration](QUALITY_DECLARATION.md) for more details.
ros-rcl 9.2.8
ROS `rcl` is a core library supporting the implementation of language-specific ROS client libraries.

Built using https://github.com/ycheng517/ros-python-wheels.

## rcl

Library to support implementation of language specific ROS Client Libraries.

Features are described in detail at [http://docs.ros2.org](http://docs.ros2.org/latest/api/rcl/index.html)

This package claims to be in the **Quality Level 1** category, see the [Quality Declaration](./QUALITY_DECLARATION.md) for more details.
ros-rosidl-typesupport-introspection-c 4.6.6
A ROS package for dynamically accessing and manipulating messages and services using C typesupport handlers.

Built using https://github.com/ycheng517/ros-python-wheels.

# rosidl_typesupport_introspection_c

`rosidl_typesupport_introspection_c` provides functionality for getting the associated message or service C typesupport handler functions and dynamically accessing or manipulating messages.

## Features

The features provided by `rosidl_typesupport_introspection_c` are described in [FEATURES](docs/FEATURES.md).

## Quality Declaration

See the [Quality Declaration](./QUALITY_DECLARATION.md) for more details.
ros-rosidl-default-runtime 1.6.0
This ROS package simplifies rosidl development by gathering and managing runtime dependencies for other rosidl packages.

Built using https://github.com/ycheng517/ros-python-wheels.

# rosidl_default_runtime

`rosidl_default_runtime` provides CMake functionality for finding and adding runtime dependencies for rosidl packages.

## Features

The *features* of this package consist entirely of serving as a gathering dependency for all runtime related dependencies of rosidl packages.
These dependencies can be found in the [package.xml](package.xml).
This helps reduce the boilerplate needed when developers create their own rosidl packages.

## Quality Declaration

This package claims to be in the **Quality Level 1** category, see the [Quality Declaration](QUALITY_DECLARATION.md) for more details.
ros-service-msgs 2.0.3
A ROS package containing fundamental message type definitions used by ROS services, including types for service introspection.

Built using https://github.com/ycheng517/ros-python-wheels.

# service_msgs

This package contains message types used by ROS services.

For more information about ROS services, check out the following links:

* [About ROS 2 interfaces](https://docs.ros.org/en/rolling/Concepts/About-ROS-Interfaces.html)
* [Understanding services](https://docs.ros.org/en/rolling/Tutorials/Beginner-CLI-Tools/Understanding-ROS2-Services/Understanding-ROS2-Services.html)

## Messages (.msg)

* [ServiceEventInfo](msg/ServiceEventInfo.msg): Part of a service event message that contains information such as timestamp and event type.
This is part of the Service Introspection feature of ROS 2 (see [REP 2012](https://ros.org/reps/rep-2012.html)).


## Quality Declaration

See the [Quality Declaration](QUALITY_DECLARATION.md) for more details.
ros-rcl-logging-spdlog 3.1.1
A ROS package providing logging functionality implemented with `spdlog`, enabling message logging and level control.

Built using https://github.com/ycheng517/ros-python-wheels.

# rcl_logging_spdlog

Package supporting an implementation of logging functionality using `spdlog`.

[rcl_logging_spdlog](include/rcl_logging_spdlog/logging_interface.h) logging interface implementation can:
 - initialize
 - log a message
 - set the logger level
 - shutdown

Some useful internal abstractions and utilities:
  - Macros for controlling symbol visibility on the library
    - [rcl_logging_spdlog/visibility_control.h](include/rcl_logging_spdlog/visibility_control.h)

## Quality Declaration

This package claims to be in the **Quality Level 1** category, see the [Quality Declaration](./QUALITY_DECLARATION.md) for more details.
ros-rosidl-typesupport-interface 4.6.6
A ROS package providing C/C++ macros that define the rosidl typesupport interface.

Built using https://github.com/ycheng517/ros-python-wheels.

# rosidl_typesupport_interface

`rosidl_typesupport_interface` is a package that provides macros that define the rosidl typesupport interface.

## Features

`rosidl_typesupport_interface` provides an interface of C/C++ macros for rosidl typesupport packages.
They are available in the `macros.h` header.

## Quality Declaration

See the [Quality Declaration](QUALITY_DECLARATION.md) for more details.
ros-rosidl-typesupport-fastrtps-c 3.6.2
A ROS package providing functionality to generate rosidl C interfaces for eProsima FastRTPS.

Built using https://github.com/ycheng517/ros-python-wheels.

# rosidl_typesupport_fastrtps_c

`rosidl_typesupport_fastrtps_c` is a package that provides functionality for generating rosidl C interfaces for eProsima FastRTPS.

## Features

`rosidl_typesupport_fastrtps_c` features are described in [FEATURES](docs/FEATURES.md).

## Quality Declaration

This package claims to be in the **Quality Level 2** category, see the [Quality Declaration](QUALITY_DECLARATION.md) for more details.
ros-ament-cmake-export-link-flags 2.5.4
Wheel for the ament_cmake_export_link_flags (ros-ament-cmake-export-link-flags) ROS 2 package.

Wheel for the ament_cmake_export_link_flags (ros-ament-cmake-export-link-flags) ROS 2 package. Built using https://github.com/ycheng517/ros-python-wheels
ros-rcutils 6.7.4
rcutils is a ROS 2 C API offering fundamental utilities, data structures, and macros for system-level operations like logging, string, and file handling.

Built using https://github.com/ycheng517/ros-python-wheels.

# rcutils: ROS 2 C Utilities data structures

`rcutils` is a C API consisting of macros, functions, and data structures used through out the ROS 2 code base.

## Quality Declaration

This package claims to be in the **Quality Level 1** category, see the [Quality Declaration](./QUALITY_DECLARATION.md) for more details.

## API

The API is a combination of parts:

- Allocator concept, used to inject the allocating and deallocating methods into a function or type.
  - rcutils_allocator_t
  - rcutils/allocator.h
- Command line interface utilities:
  - rcutils/cmdline_parser.h
- Utilities for setting error states (error message, file, and line number) like `strerror` for `errno`:
  - rcutils/error_handling.h
- Some basic filesystem utilities like checking for path existence, getting the cwd, etc...:
  - rcutils/filesystem.h
- A C string find method:
  - rcutils_find()
  - rcutils_find_last()
  - rcutils/find.h
- A convenient string formatting function, which takes a custom allocator:
  - rcutils_format_string()
  - rcutils/format_string.h
- Functions for interfacing with process environment variables:
  - rcutils_get_env()
  - rcutils_get_home_dir()
  - rcutils_set_env()
  - rcutils/env.h
- Extensible logging macros:
  - Some examples (not exhaustive):
    - RCUTILS_LOG_DEBUG()
    - RCUTILS_LOG_INFO_NAMED()
    - RCUTILS_LOG_WARN_ONCE()
    - RCUTILS_LOG_ERROR_SKIPFIRST_NAMED()
  - rcutils/logging_macros.h
  - rcutils/logging.h
- Some basic utilities to load, unload and get symbols from shared libraries at run-time.
  - rcutils/shared_library.h
- A string replacement function which takes an allocator, based on http://creativeandcritical.net/str-replace-c:
  - rcutils_repl_str()
  - rcutils/repl_str.h
- String splitting functions which take a custom allocator:
  - rcutils_split()
  - rcutils_split_last()
  - rcutils/split.h
- A version of `strdup` which takes an allocator:
  - rcutils_strdup()
  - rcutils/strdup.h
- Portable implementations of "get system time" and "get steady time":
  - rcutils_system_time_now()
  - rcutils_steady_time_now()
  - rcutils_raw_steady_time_now()
  - rcutils/time.h
- Some useful data structures:
  - A "string array" data structure (analogous to `std::vector<std::string>`):
    - rcutils_string_array_t
    - rcutils/types/string_array.h
  - A "string-string map" data structure (analogous to `std::map<std::string, std::string>`)
    - rcutils_string_map_t
    - rcutils/types/string_map.h
- Macros for controlling symbol visibility and linkage for this library:
  - rcutils/visibility_control.h
ros-type-description-interfaces 2.0.3
This ROS package offers message and service definitions for describing and communicating ROS interface type descriptions.

Built using https://github.com/ycheng517/ros-python-wheels.

# type_description_interfaces

A package containing message and service definitions for describing and communicating descriptions of other types.

## Messages (.msg)

* [Field](msg/Field.msg): Represents a single field in a ROS Interface Type
* [FieldType](msg/FieldType.msg): Represents the type of a single field in a ROS Interface Type
* [IndividualTypeDescription](msg/IndividualTypeDescription.msg): Represents a single ROS Message Type by itself
* [TypeDescription](msg/TypeDescription.msg): Represents a single ROS Message Type along with all referenced types

## Quality Declaration

See the [Quality Declaration](QUALITY_DECLARATION.md) for more details.

## TODO

* Should we pick limits (bounds) for strings in these types, e.g. type names, default values, etc?
* Should we pick limits (bounds) for sequences in these types, e.g. number of referenced types?
* Consider how to support constants and annotations (currently excluded) and potentially enums in the future.
* Consider using padding in `IndividualTypeDescription.msg` to support back porting efforts.
ros-rosidl-runtime-cpp 4.6.6
A ROS package that generates and provides C++ runtime ROSIDL interface files for message and service definitions.

Built using https://github.com/ycheng517/ros-python-wheels.

# rosidl_runtime_cpp

`rosidl_runtime_cpp` is a package generates and provides runtime ROSIDL interfaces files in C++.

## Features

The features provided by `rosidl_runtime_cpp` are documented in its [feature documentation](docs/FEATURES.md).

## Quality Declaration

See the [Quality Declaration](QUALITY_DECLARATION.md) for more details.