semvec/pypi-packages huggingface dataset:
Connect-to-Server-CPS 0.1.1
Demo library

## About The Code

This is a part of the project that we are working on it for the Cyber-Physical Group (i6) at the Technical University of Munich. This package would connect to a server, find the LaTeX files, integrate the LaTeX's input and include functions, and save the file at a new directory defined by user. No matter how many files the directory in the server contains. The code will go through each folder and find the LaTeX files and write them at the new directory maintaining the directory structure in the server.
## How to install

You can install it by running the following line in your terminal:
```
pip install Connect_to_Server-CPS
```

## Getting Started

This is an example of how you may give instructions on setting up your project locally.
```Python
from Connect_to_Server import Connection

host = "archive.cps.in.tum.de" #The host of the server
username = "your username"
password = "your password"
directory = "/mnt/current/BachelorTheses/2014/" #The directory that you want to find the LaTeX files
Save_at = "D:/CPS/HiWiProjects/Parse/data" #The new directory that you want to save the integrated LaTeX files

C = Connection.Connection(host,username,password) #You are ready to connect to the server.

C.Find_and_Integrate(directory,new_directory)

#Note: you can also run terminal commands. For example, you can run the following code to find the folders in the directory in the server:

# Connect = C.Connect()
# ssh_stdin, ssh_stdout, ssh_stderr = Connect.exec_command("ls " + directory)
# for line in ssh_stdout: print(line.strip())

```
ngobot-json 1.1.9
A Python JSON Format
Requires Python: >=3.6

# SIMPLE PYTHON JSON FORMAT 
The repository contain a script to format your python response in a correct JSON format using the standard HTTP response codes. Well suitable to backend applications with REST API building concept in mind.

**Install the ngobot-json package**

`pip install ngobot-json`

**import the ngobot-json package**

`from ngobot_json.pyresponse import JsonResponse`

**1. Success Response**

you can simply return json successful response format in this way.

_e.g._

`response = JsonResponse()

print(response.Success())
`

_Output:_


`{
"status":200,
"message":"Successful",
"data":{
"status":200,
"message":"ok",
"reason":"Successful"
}
}`

You can modify the json success response format by passing two arguments: (1) the data to return as response and (2) the keyword indicator "success" to activate success response format.

_e.g. User Account Created._

`

task = "User Account successfully created"

response = JsonResponse(task, "success")

print(response.Created())

`

_Output:_

`
{
"status":201,
"message":"Created Successfully",
"data":{
"status":200,
"message":"ok",
"reason":"User Account successfully created"
}
}
`
_e.g. Process completed successfully_


`task = "The Process is successfully completed"

response = JsonResponse(task, "success")

print(response.Success())`



Output:


`{"status": 200, "message": "Successful", "data": {"status": 200, "message": "ok", "reason": "The Process is successfully completed"}}
`

**2. Error Response**

The error response follows the same pattern of the success modify response, but has a different keyword argument "error" to activate the error response format:

_e.g._

`task = "Invalid username and password"

response = JsonResponse(task, "error")

print(response.Unauthorized())`

_Output:_

`{
"status":401,
"message":"Unauthorized",
"data":{
"status":422,
"message":"Unprocessable Entity",
"reason":"Invalid username and password"
}
}`



**3. Adding External json return from another function or database.**
note that in this section we use keyword "data" to activate the json format with external json file.

_e.g._ 


`task = {
"status":201,
"message":"Created Successfully",
"data":{
"status":200,
"message":"ok",
"reason":"User Account successfully created"
}
}

response = JsonResponse(task, "data")

print(response.Success())`


Output:

`{"status": 200, "message": "Successful", "data": {"status": 201, "message": "Created Successfully", "data": {"status": 200, "message": "ok", "reason": "User Account successfully created"}}}
`



**4. List of All the supported HTTP codes functions to call.**

comming soon.
sphinxcontrib-constdata 1.0.5
Sphinx extension that allows showing values, tables, and links from CSV files. Instead of hard-coding values in the text, you write constants or queries replaced with value(s) from the CSV file. If the file contains language-depending strings, they can be translated with the rest of the Sphinx docs.

.. |project| replace:: sphinxcontrib-constdata

.. image:: docs/img/logo.svg
   :align: right

#########
|project|
#########

.. image:: https://gitlab.com/documatt/sphinxcontrib-constdata/badges/master/pipeline.svg
    :target: https://gitlab.com/documatt/sphinxcontrib-constdata/

.. the rest of file included in docs/index.rst

|project| is the extension for `Sphinx documentation <https://www.sphinx-doc.org/>`_ projects that allows showing values, listing tables, and generating links from CSV, JSON and YAML files. Instead of hard-coding values in the text, you write constants or queries replaced with value(s) from the external file(s). If the file contains language-sensitive strings, they can be translated with the rest of the Sphinx docs.

* docs: https://documatt.gitlab.io/sphinxcontrib-constdata
* code: https://gitlab.com/documatt/sphinxcontrib-constdata where issues and contributions are welcome

*****
About
*****

|project| started from the urge to manage thousands of external strings like UI labels, keyboard shortcuts, etc., used in a large enterprise application's docs. Devs and translators often change these strings. Idea of hard-coding these strings in the docs, and manually watching changes and updating them across the docs, scared me so much that I developed this Sphinx extension.

.. tip:: You can read about my other Sphinx documentation tools and tech writing tips, tricks, and insights at `Tech writer at work <https://techwriter.documatt.com>`_ blog.

*********
Impressum
*********

|project| is open source licensed under BSD3.

Project logo and icon "table-multiple" provided by `materialdesignicons.com <https://materialdesignicons.com/icon/table-multiple>`_.