Braintree initializer for the Pyramid Web Framework. 100% Test Covered.
The following configuration options are required in your config.ini:
pyramid.includes = pyramid_braintree braintree.environment = sandbox braintree.merchant_id = MY_MERCHANT_ID braintree.public_key = MY_PUBLIC_KEY braintree.private_key = MY_PRIVATE_KEYThe following configuration options are supported for environment:
development
production
sandbox
Additionally, the use_unsafe_ssl option may be specified (otherwise, this configuration wisely defaults to False):
braintree.use_unsafe_ssl = True
0.1.1 (2013-07-02)
Relying on Pyramid’s asbool helper for more robust boolean detection.
0.1 (2013-06-27)
Allow for the following Braintree configuration options: environment, merchant_id, public_key, and private_key
1 maintainer
Metadata
1 maintainer
Release files for pyramid_braintree 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pyramid_braintree-0.1.1.tar.gz | 3.7 kB | Without provenance | Details |
Release files / pyramid_braintree-0.1.1.tar.gz
| Download URL | pyramid_braintree-0.1.1.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6f0be4c5f7e045530ac2d4dec3d742a3229fceef91cdc179ed06b73c3b2ef6e8
|
|
BLAKE2b-256 checksum How to use checksums |
35516e16f8ce8342ddfbc915f9381ecd47d5b5ab6862ea092b8ed0d1950a2473
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pyramid_braintree 0.1.1
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.
