package up for PyPI

[Google Code Exporter]

What steps will reproduce the problem?
1.pip search fabricate

What is the expected output? What do you see instead?

  I expect to see fabricate listed :)  Instead... I don't.

What version of the product are you using? On what operating system?

  Any version up to May 3rd, 2013

Please provide any additional information below.

  IWBNI projects that I work on could set up fabricate as a build-depends much like other python test tools and etc.

Original issue reported on code.google.com by [e-mail] on 27 May 2013 at 2:13

[Google Code Exporter]

Issue 41 has been merged into this issue.

Original comment by [e-mail] on 27 May 2013 at 2:21

• Added labels: ****
• Removed labels: ****

[Google Code Exporter]

Good idea!

Original comment by [e-mail] on 27 May 2013 at 2:22

• Added labels: ****
• Removed labels: ****

[Google Code Exporter]

I will take a look at this. 

I guess it goes under the banner of promoting fabricate. Will also look a 
making sure we have a wikipedia entry and some cross linking with pages related 
to build tools on wikipedia.

Any other ideas on how to attract a few more users?

Original comment by [e-mail] on 28 May 2013 at 11:43

• Changed state: Accepted
• Added labels: ****
• Removed labels: ****

[Google Code Exporter]

Good question.

To be honest, I'm not sure adding one's own Wikipedia page is a good idea. 
Wikipedia has notability guidelines (see 
http://en.wikipedia.org/wiki/Wikipedia:Notability#General_notability_guideline),
 and I'm not sure fabricate would count at this stage in its life, os it may 
well be deleted. Besides, I don't think it's actually a very practical form of 
promotion.

I think http://www.reddit.com/r/programming/ and 
http://www.reddit.com/r/Python/ would be a good start -- I'd be happy to 
promote it there (again?). Send me an email once it's on PyPI, and I'll promote 
it there.

To get on PyPI, you basically need to add a setup.py, and then a PyPI account 
(easy to get) and upload it. See my symplate project for an example: 
https://github.com/benhoyt/symplate

It'd probably be a good idea to add a LICENSE.txt to the source control instead 
of having a separate License wiki page.

There's a good guide to "creating a Python package" here: 
http://guide.python-distribute.org/creation.html

Original comment by [e-mail] on 28 May 2013 at 10:18

• Added labels: ****
• Removed labels: ****

[Google Code Exporter]

I went ahead and created a branch of fabricate and hosted it on github here: 
https://github.com/JDeuce/fabricate

I also submitted it to PyPI, so now pip, easy_install, etc users can get 
fabricate.
https://pypi.python.org/pypi/fabricate/

If this project is still active, and someone pulls my changes into the 
mainline, I can transfer ownership of the PyPI project to the maintainers here. 
Otherwise I guess I'll maintain it myself.

- J

Original comment by [e-mail] on 14 May 2014 at 2:56

• Added labels: ****
• Removed labels: ****

[Chris Coetzee]

It might be a good time to claim the project on pypi, and merge the current setup.py file here.