-------------------------
This is a Turbogears meta package that lists the exact packages and versions that common
Turbogears installs need to run.
We list the packages here so you can make a standard setup.py without messing around with pip
freeze, or performing a non standard install using the Turbogears Repository.
Use this package if
-------------------------------
Have you ever wanted to deploy a python package with Turbogears as a dependency but
are worried what will be installed with the single tg.devtools/Turbogears2 dependency?
Have you ever installed Turbogears on your dev machine then come to install your package
that depends on Turbogears on a prod machine only to find that one of the packages
Turbogears depends on has changed, breaking your prod install?
Do you want to tell your users to just pip install <your package> that relies on Turbogears, rather
that having to tell them to run a custom command first to install Turbogears from the TG Repo.
Do you want to use the command::
pip install --upgrade Turbogears2Frozen
to get the latest Turbogears
Using
-------------------------------
TG2Frozen has all the standard dependancies apart from MYSQL-python (as you may be using a different DB) and it
does not contain a specific sqlalchemy version, as there are backward compatibility issues and you may want to
use a particular version.
Your application's **setup.py** might look like::
import setuptools
from distutils.core import setup
from sys import version
from setuptools import find_packages
setup(name='MyPackageUsingTG',
install_requires=(
"""
TurboGears2Frozen==2.2.0
SQLAlchemy==0.7.0
MySQL-python==1.2.3
"""
),
version='0.0.1',
description='My package that uses Turbogears2 but doesn't have loads of dependencies listed',
author='Joe Bloggs',
author_email='joe@bloggs.c',
packages=find_packages(exclude=['ez_setup'])
)
Problems
-------------------------------
This package works for my stuff, but I expect it will not for everyone so please email me if you feel
that other packages should be included.
I'll update this package as I need the updates, if you need something sooner give me a mail.
I'm going to keep the numbering the same as the underlying TG package, may be increment it by a fourth
number if a TG dependency needs updating.
Thanks
Metadata
Release files for TurboGears2Frozen 2.2.0
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 | Actions |
|---|---|---|---|---|
| TurboGears2Frozen-2.2.0.tar.gz | 1.7 kB | Without provenance | Details for TurboGears2Frozen-2.2.0.tar.gz |
Release files / TurboGears2Frozen-2.2.0.tar.gz
| Download URL | TurboGears2Frozen-2.2.0.tar.gz |
|---|---|
| Size | 1.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f757dedef5ee64a3349640b10179c5179a1478cc71a9f3a3ca76649576b55200
|
|
BLAKE2b-256 checksum How to use checksums |
c301c100f3f8aa3baf314452da38bfab956a29465fa2c029396d42ae56201138
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for TurboGears2Frozen 2.2.0
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.