# PipCreate
[](http://badge.fury.io/py/PipCreate)
[](https://travis-ci.org/Carreau/PipCreate)
[](https://pypi.python.org/pypi/PipCreate)
Creating Python package make simple.
Because you should be focused on the feature of your packages, not on the hosting
testing building infrastructure.
- [x] Choose package name if you have no idea.
- [x] check that the name is not taken
- [x] set up github remote
- [x] hook up travis-ci with Github
- [ ] hook Read the doc with Github
- [ ] hook covertall with Github
- [ ] help build and release
- [ ] refuse to put on PyPi if travis failing
But as example are better:
```bash
$ python3 -m pipcreate frobulator
will use target dir /Users/bussonniermatthias/eraseme
# Will open github at the right page and ask you for a private token at first launch.
Comparing "frobulator" to other existing package name...
# Genrate Package name if you have no idea
frobulator seem to have a sufficiently specific name
Logged in on GitHub as Matthias Bussonnier
Workin with repository Carreau/frobulator
Clonning github repository locally
Cloning into 'frobulator'...
warning: You appear to have cloned an empty repository.
Checking connectivity... done.
I am now in /Users/bussonniermatthias/eraseme/frobulator
Travis user: Matthias Bussonnier
syncing Travis with Github, this can take a while...
......
syncing done
Enabling travis hooks for this repository
Travis hook for this repository are now enabled.
Continuous interation test shoudl be triggerd everytime you push code to github
/Users/bussonniermatthias/eraseme/frobulator
# clone, do the first commit
# re-push and open travis on build page to be sure all is right.
```
Rely heavily on other packages, TraviPy, pygithub and cookiecutter.
While cookiecutter is nice and allow a lot of flexibility, I think it require too much thinking
or is too frightening when you don't have time to loose or is a beginnier.
Pipcreate will make most decision for you allowing you to focus on what you like to.
History
-------
0.1.0 (2014-01-11)
---------------------
* First release on PyPI.
[](http://badge.fury.io/py/PipCreate)
[](https://travis-ci.org/Carreau/PipCreate)
[](https://pypi.python.org/pypi/PipCreate)
Creating Python package make simple.
Because you should be focused on the feature of your packages, not on the hosting
testing building infrastructure.
- [x] Choose package name if you have no idea.
- [x] check that the name is not taken
- [x] set up github remote
- [x] hook up travis-ci with Github
- [ ] hook Read the doc with Github
- [ ] hook covertall with Github
- [ ] help build and release
- [ ] refuse to put on PyPi if travis failing
But as example are better:
```bash
$ python3 -m pipcreate frobulator
will use target dir /Users/bussonniermatthias/eraseme
# Will open github at the right page and ask you for a private token at first launch.
Comparing "frobulator" to other existing package name...
# Genrate Package name if you have no idea
frobulator seem to have a sufficiently specific name
Logged in on GitHub as Matthias Bussonnier
Workin with repository Carreau/frobulator
Clonning github repository locally
Cloning into 'frobulator'...
warning: You appear to have cloned an empty repository.
Checking connectivity... done.
I am now in /Users/bussonniermatthias/eraseme/frobulator
Travis user: Matthias Bussonnier
syncing Travis with Github, this can take a while...
......
syncing done
Enabling travis hooks for this repository
Travis hook for this repository are now enabled.
Continuous interation test shoudl be triggerd everytime you push code to github
/Users/bussonniermatthias/eraseme/frobulator
# clone, do the first commit
# re-push and open travis on build page to be sure all is right.
```
Rely heavily on other packages, TraviPy, pygithub and cookiecutter.
While cookiecutter is nice and allow a lot of flexibility, I think it require too much thinking
or is too frightening when you don't have time to loose or is a beginnier.
Pipcreate will make most decision for you allowing you to focus on what you like to.
History
-------
0.1.0 (2014-01-11)
---------------------
* First release on PyPI.
Release files for pipcreate 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 | |
|---|---|---|---|
| pipcreate-0.1.1.tar.gz | 13.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pipcreate-0.1.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 20.8 kB
Release files / pipcreate-0.1.1.tar.gz
| Download URL | pipcreate-0.1.1.tar.gz |
|---|---|
| Size | 13.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f693ab5373873bb070b8e4b10cd6d9bb86f37883e6399de15e2c4e1439f1a826
|
|
BLAKE2b-256 checksum How to use checksums |
498af2fb18d355080c6cf9fe1bac3008ba569f642b604630984c1b5fce57b1d7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / pipcreate-0.1.1-py2.py3-none-any.whl
| Download URL | pipcreate-0.1.1-py2.py3-none-any.whl |
|---|---|
| Size | 7.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
783642fe6581c1c4c09f6385a8184abe93fc1131f20f751fb4de23ed113f085d
|
|
BLAKE2b-256 checksum How to use checksums |
9f188c210edd031091fb476bbb36c9d11e0b99b11ecc4b2c17a6a6e542351133
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |