21.03.2011 20:35, Tomer Filiba kirjoitti:
1) yes, the changelog is on the site.
2) why not? if it makes life easier for people, why not build the
packages for them? it takes 3 more seconds on my part.
Seems pointless to me -- whose lives will they make easier? Sure enough,
if it doesn't take more time than that, then it doesn't matter either way.
3) i *have* updated pypi (with setup.py register):
http://pypi.python.org/pypi/RPyC/ it shows the latest version and has
the download location.
also, http://pypi.python.org/simple/RPyC/ shows the correct download
location for 3.1.0.
no idea why it would fail... i'll upload the files directly (setup.py
upload fails too)
What error is "setup.py sdist upload" giving you?
Also, installation (both easy_install and pip) is failing now because
the line endings in the tarball/zip seem to be CRLF and not LF, so it
gives a syntax error when exec'ing version.py during setup.
-tomer
An NCO and a Gentleman
2011/3/21 Alex Grönholm <[email protected]
<mailto:[email protected]>>
21.03.2011 19:53, Alex Grönholm kirjoitti:
I see that you've released 3.1.0 already. I'd like to give my
2 cents on the release process itself.
First of all, I don't see a changelog anywhere. It'd be very
helpful for users to know what new features there are and
which bugs were fixed in this release.
I had written this before the release announcement came in, and I
see there is a changelog on the website at least.
Second, why are you building eggs for RPyC? A Windows
installer I can understand, but eggs seem rather pointless to
distribute, especially since RPyC does not have any C
extensions. Eggs are being phased out anyway. All you really
need to upload is the tarball (python setup.py sdist) and the
win32 installer.
Third, consider uploading the tarball (+ any Windows
installers) to PyPI. If I try installing RPyC right now using
pip (pip install rpyc), all I get is the old 3.0.7 version.
Easy_install, however, gives me "3.1.0-pre", which isn't quite
right either.
