This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description

# Python Code Examples

This will guide you through the steps necessary to set up credentials and start playing with the sample code. Note that once you’ve set up credentials for one language, you don’t need to re-create them for another language. If you set up the credentials for python, php will use the same credentials.

These instructions expect that you are in the examples/python subdirectory of the github repository.

# Authentication and Provisioning The easiest way to walk through the needed provisioning and authentication to get your credentials is by following the instructions on [Authorizing your Client]( from the Getting started guide on our site. Once you have done this, you’ll be able to run the ‘diagnostic tools’ example scripts.

## Credential File Creation You can get your credentials set up for use by the sample code by using the command in the examples/python directory: `bash $ ./ `

When you run with no command line options, the script will create a ‘default’ section in your ~/.edgerc file. For examples other than you’ll need to pass the name of the appropriate section as an argument, for example this is how you’d set up `bash ./ ccu `

You can find the correct name for the credentials section on the “section=” line in the example script. If you run the script again for a specific section (including ‘default’) it will overwrite the previous credentials with your new ones.

## Diagnostic Tools - The first example code to test is the script. The credentials from the creation step give you permission to run the “dig” command from the API.

` bash ./ `

This simple script runs the ‘locations’ call to find out where the Akamai servers are located. The API can run the ‘dig’ for you from any of these locations. Once it has done that, it grabs one at random and makes the dig call from there.

By reviewing the code you can see how simple it is to make API calls.

All of the sample code in the directory also supports –verbose to see the output on the screen, and/or –debug to see all of the HTTP traffic. These flags can help enormously in figuring out what’s going wrong or how it’s working.

` bash ./ --verbose ./ --debug `

## CCU (Purge) - We have a [blog post]( with instructions on getting set up with the CCU API. Prerequisites: ccu credentials and edit the filename to a valid file on your system

Release History

Release History


This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
akamaikickstart-1.0.0-py2-none-any.whl (2.0 kB) Copy SHA256 Checksum SHA256 2.7 Wheel Oct 10, 2016
akamaikickstart-1.0.0.tar.gz (2.1 kB) Copy SHA256 Checksum SHA256 Source Oct 10, 2016

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting