Skip to content
This repository has been archived by the owner on Dec 29, 2022. It is now read-only.

Python Install Packaging & Instructions #22

Closed
GoogleCodeExporter opened this issue Mar 7, 2015 · 14 comments
Closed

Python Install Packaging & Instructions #22

GoogleCodeExporter opened this issue Mar 7, 2015 · 14 comments

Comments

@GoogleCodeExporter
Copy link

I'm sure I'll figure it out eventually, but it would be nice if it was easy.

Original issue reported on code.google.com by jack.sankey@gmail.com on 13 Aug 2008 at 8:51

@GoogleCodeExporter
Copy link
Author

Yeah, sorry I haven't figured out a good way to package this yet. Currently the 
zip
just has all the source files and you'll need to install the third party 
packages it
depends (listed on the wiki). I'm trying to figure out how to make an egg out of
this, similar to a java jar so that it's easier to use. Any suggestions for 
packaging
the files? Anyone who's created eggs before have any helpful pointers?

Original comment by arkajit.dey on 13 Aug 2008 at 11:38

  • Changed title: Python Install Packaging & Instructions
  • Changed state: Accepted
  • Added labels: Implementation-Python

@GoogleCodeExporter
Copy link
Author

Just use the distutils and create a setup.py, this will build the egg. 
http://docs.python.org/dist/dist.html

Original comment by david.vo...@gmail.com on 14 Aug 2008 at 9:24

@GoogleCodeExporter
Copy link
Author

I sent a setup.py to the mailing list on Aug 14th (and I've attached a slightly
updated one here).

You can use it to create the distribution by issuing "python setup.py sdist", 
or to
install the module with "python setup.py install". Running it with --help or
--help-commands will display a number of other (possibly) useful operations.

The setup.py script I posted to the list was strictly distutils-based, the one 
I've
attached here will use setuptools if it's installed. If you want an egg simply 
run
"python setup.py bdist_egg" (the egg can be found in dist/). 

Original comment by j.eric.e...@gmail.com on 20 Aug 2008 at 9:04

Attachments:

@GoogleCodeExporter
Copy link
Author

Any chance of getting this on PyPi so that it can be included as a dependency 
and easily installed via pip or easy_install?

Original comment by james.thornton on 18 Jun 2011 at 5:21

@GoogleCodeExporter
Copy link
Author

Regarding comment 4 about PyPi:
I don't have the bandwidth to work on getting Keyczar into PyPi. I would also 
like to get more review and testing for the Python version in general.

Original comment by steve.w...@appdirect.com on 21 Jun 2011 at 10:55

@GoogleCodeExporter
Copy link
Author

You can install with pip like this:
pip install 
http://keyczar.googlecode.com/files/python-keyczar-0.6b.061709.tar.gz

Original comment by lawlor.chris on 25 Sep 2011 at 3:26

@GoogleCodeExporter
Copy link
Author

I would be willing to help get KeyCzar into PyPI. If I submit a patch that adds 
code to register the package and you accept it, all you would have to do then 
is run the setup.py script. Alternatively I would be willing to do that for you.

Would you be willing to accept a patch like this?

-adam
--
Adam Feuer
Seattle, WA

Original comment by adamfe...@gmail.com on 28 Dec 2011 at 1:13

@GoogleCodeExporter
Copy link
Author

Ok, I uploaded keyczar to pypi, you can see it here:

http://pypi.python.org/pypi/python-keyczar/0.7b

To do the upload, I created a .pypirc file as described here:

http://packages.python.org/an_example_pypi_project/setuptools.html

Then I ran the commands:

    python setup.py register
    python setup.py sdist upload

I think you can update this package when you release future versions. Let me 
know if that doesn't work. I made changes to only one file, the setup.py, you 
can see it here:

http://code.google.com/r/adamfeuer-pypi/source/browse/python/setup.py

I have attached a patch for the file in case that is better. Or if you want it 
in some other format, will you let me know? The patch is the same one I posted 
to the keyczar-discuss mailing list.

cheers
adam
--
Adam Feuer

Original comment by adamfe...@gmail.com on 31 Dec 2011 at 10:11

Attachments:

@GoogleCodeExporter
Copy link
Author

I have modified Adam's setup.py to use setuptools, which allows "pip install" 
to download all the required dependencies. This makes using KeyCzar 
significantly easier. Would anyone from Google be willing to accept a patch? 
I've signed Google's open source contributor agreement before.

I'll also try to get the pypi version updated to the latest one...

Original comment by e...@lectorius.com on 25 Jun 2012 at 7:04

@GoogleCodeExporter
Copy link
Author

Please accept the patch from June 25th, 2012. It's pretty standard, safe stuff 
in the Python world.

I'm happy to help keep PyPI updated too as Keyczar makes new releases.

Original comment by yoavshap...@gmail.com on 28 Jan 2013 at 10:15

@GoogleCodeExporter
Copy link
Author

I'll be happy to take a look at the patch and roll it in. I see Adam's patch 
from Dec 2011, and EJ's comment from June 2012 saying he'd modified it, but I 
don't see the modified version.

Original comment by swillden@google.com on 28 Jan 2013 at 10:29

@GoogleCodeExporter
Copy link
Author

Attached my patch. I've been using this version for a bit, and just rebased it 
for the latest release (hopefully I did it correctly)! The advantage with this 
version is that pip will actually install the dependencies (pyasn1 for keyczar, 
and pycrypto for the main code. I think I may also be a maintainer for the 
package in PyPI. It looks like I need to update the version that is there!

Original comment by e...@evanjones.ca on 29 Jan 2013 at 2:58

Attachments:

@GoogleCodeExporter
Copy link
Author

svn checkout + manual merge of the patch works for me locally with pip install, 
so that's good. Looks good to merge into master (or whatever the head is called 
on Google Code.)

Original comment by yoavshap...@gmail.com on 29 Jan 2013 at 2:15

@GoogleCodeExporter
Copy link
Author

Merged to head.

Original comment by swillden@google.com on 6 Feb 2013 at 6:30

  • Changed state: Fixed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant