Skip to main content
# request_factory client
[![Build Status](https://travis-ci.org/tinyclues/request_factory.svg?branch=master)](https://travis-ci.org/tinyclues/request_factory) [![Coverage Status](https://coveralls.io/repos/github/tinyclues/request_factory/badge.svg?branch=delete_package)](https://coveralls.io/github/tinyclues/request_factory?branch=delete_package)

This is for simplify the request management.
Actually support :
* http

## Contributing to request_factory client

All contributions, bug reports, bug fixes, documentation improvements, enhancements and ideas are welcome.

### Working with the code

Now that you have an issue you want to fix, enhancement to add, or documentation to improve, you need to learn how to work with GitHub.
We use the [Github Flow](https://guides.github.com/introduction/flow/)

Finally, commit your changes to your local repository with an explanatory message, request_factory client uses a convention for commit message prefixes.
Here are some common prefixes along with general guidelines for when to use them:
* ENH: Enhancement, new functionality
* BUG: Bug fix
* DOC: Additions/updates to documentation
* TST: Additions/updates to tests
* BLD: Updates to the build process/scripts
* PERF: Performance improvement
* CLN: Code cleanup
* NOBUILD: special tag to skip test & build

Metadata

Release files for request_factory 2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for request_factory 2
File Interpreter ABI Platform
request_factory-2-py2-none-any.whl Python 2 none any Details

Release files / request_factory-2-py2-none-any.whl

Download URL request_factory-2-py2-none-any.whl
Size 5.2 kB
Tags Python 2
SHA-256 checksum
How to use checksums
4a779937f2ee69115a521b0f8edb5aff978dd1ac104a6c8d59ce2e6b23f9cc42
BLAKE2b-256 checksum
How to use checksums
67be77c2ebe9fc172e469a62ea5d455b449da6f2a73461ecfc3588509799751d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for request_factory 2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

2 This release

1 release file No provenance

1

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page