Open GoogleCodeExporter opened 8 years ago
Attached is a quick cut at a Python setup.py. I think I've got everything
correct as
of the current, 0.1.2, release but please review it first.
setup.py will quite happily live alongside the various language implementations
but
it might be better to put mimeparse.py in a "python" directory along with
setup.py.
Hope this helps! It would be lovely to see mimeparse appear at PyPI,
http://pypi.python.org/pypi, soon :).
Original comment by matt.goo...@gmail.com
on 24 Nov 2008 at 10:59
Attachments:
looks fine to me
Original comment by peter.fein
on 24 Nov 2008 at 11:36
PyPi is waiting for the new tarball with that setup.py script
http://pypi.python.org/pypi/mimeparse/0.1.2
Original comment by wik...@asturlinux.org
on 13 Apr 2009 at 10:13
sorry, I forgot to attach the tarball (based on the setup.py provided by matt
goodall)
Original comment by wik...@asturlinux.org
on 13 Apr 2009 at 10:25
Attachments:
...it's currently there as both 'mimeparse' and 'python-mimeparse'. Which is
official?
Original comment by pjimen...@gmail.com
on 9 Oct 2013 at 6:15
Could you upload current mimeparse (0.1.4) to the cheeseshop?
pip won't download external files by default any more, so its much more
convenient for users (and arguably, more secure) for it to be hosted directly
there. (i.e a `python setup.py sdist upload`)
Original comment by teh....@gmail.com
on 10 Feb 2014 at 8:56
Original issue reported on code.google.com by
peter.fein
on 6 Mar 2008 at 3:21