Re: [Distutils] Full egg name
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Forgot to cc the list... Tarek Ziadé skrev:
On Fri, Mar 26, 2010 at 2:04 PM, Martin Raspaud
wrote: [..] What I want to do is to generate tarballs for our production servers (that have no compiling tools).
I am not sure but, if you are planning to distribute a buildout for you production server, what you could do is zip a buildout you have built in a similar environment (==a binray release of your buildout) that contains all the eggs in eggs/ and possibly a download cache within the buildout (download/)
Then unzip in on your production server, and with the proper options set in you cfg file, you can make sure the server will not access pypi or anythong else, and use the local cache and eggs,
That's how I do (with some scripts located in collective.releaser), and they are alternatives.
Packaging an entire buildout environment is not really an option I think, since we have several projects using the same eggs, and we think it would be cleaner to share them (I'm thinking especially of big eggs, like scipy and numpy). On the other hand, I looked at collective.releaser and it is tempting. I will talk about this with my boss.
The tarball should hold /myproject/myproject-0.3.0-py2.6-macosx-10.3-fat/<all files> in a compiled form (as would be the result of setup.py bdist)
The info you gave me is usefull for locally developped packages that I can install as develop eggs. However some of them should be retreived from git, but I thought downloading them first, then put them as develop eggs.
These packages are part of your buildout project or not ? If they are, you can use a project like "mr.developer" to get those locally.
Yes there are. I didn't know about mr.developer, looks nice, thanks ! As for git, I am using zerokspot.recipe.git to retrieve them as develop eggs.
But again, I am not sure about your release process and how these packages are included in your environment so..
If you just want to create standalone binary distributions of single python packages, I am not sure how buildout is related, and why you are doing a recipe.
Buildout is interesting to me because I can develop, test and use packages in a clean environment. I don't need to take care of any PYTHONPATH, all dependencies are installed automatically, and so on. So it is a great tool for development, and I got this from your book (which is really great by the way). As such I want to have a recipe for automatically creating packages to deploy on our servers. I see that it is indeed not buildout's philosophy build isolated eggs, but it is not the only thing I use it for :), it is a mere packaging tool for our production system I am building. Regards, Martin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJLrMAtAAoJEBdvyODiyJI4cjoIAL7o1s7WjR0QSgEgQBSJXaxa 9nlQeFSx0y2ovK4fd3AX/m0FSj4KSf/yiJkG1BDoEPgeaptqUX2lzzp/0XdFbGDn 0t1eSoEL04Py+9eB8FJDzY42vozn54lPo/4cAa9wXW1WQQUJDNkJVh7nm+IYZWei 6PbPT3rY7ETAJAKHcREoAOtJcdrVeU9WhGwEF6nklzmsLNUaEB7kImBisCb/yNKa soEOXr7j5fc6D8ZCbiOyrtbsnrhcKC1EF+J+0e6bvVTftueCywON1fjULKlelyv1 y7KEPkbMr8o88EAluyW7V21NZ7qZDBkaUoVl8erE6hS8uHBODNzeL2KT0i66j88= =gjh8 -----END PGP SIGNATURE-----
On Fri, Mar 26, 2010 at 3:09 PM, Martin Raspaud
Packaging an entire buildout environment is not really an option I think, since we have several projects using the same eggs, and we think it would be cleaner to share them (I'm thinking especially of big eggs, like scipy and numpy).
It really depends on your needs and constraints. I had to ship full releases to customers. In your case, you could share the same downloads and eggs folders on your productions servers maybe, or run your own PyPI private server to serve the archives to your buildouts when they claim it. [..]
Buildout is interesting to me because I can develop, test and use packages in a clean environment. I don't need to take care of any PYTHONPATH, all dependencies are installed automatically, and so on. So it is a great tool for development, and I got this from your book (which is really great by the way).
Great to hear the book helps :) As a matter of fact, I wrote it right after I had set up a process for a generic release story with buildouts at a Plone company, to help developers ship their applications to the customers.
As such I want to have a recipe for automatically creating packages to deploy on our servers. I see that it is indeed not buildout's philosophy build isolated eggs, but it is not the only thing I use it for :), it is a mere packaging tool for our production system I am building.
It makes sense. I use buildout for most web applications production environments, and I think many people do. It's just harder to sell if you have a sysadmin in front of you, that is used to other tools ;) Tarek
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tarek Ziadé skrev:
On Fri, Mar 26, 2010 at 3:09 PM, Martin Raspaud
wrote: [..] Packaging an entire buildout environment is not really an option I think, since we have several projects using the same eggs, and we think it would be cleaner to share them (I'm thinking especially of big eggs, like scipy and numpy).
It really depends on your needs and constraints. I had to ship full releases to customers.
In your case, you could share the same downloads and eggs folders on your productions servers maybe,
Yes, indeed.
or run your own PyPI private server to serve the archives to your buildouts when they claim it.
That looks tempting, but is it possible to have a private pypi server distributing binary (ready compiled) eggs ? I explore these options anyway.
As such I want to have a recipe for automatically creating packages to deploy on our servers. I see that it is indeed not buildout's philosophy build isolated eggs, but it is not the only thing I use it for :), it is a mere packaging tool for our production system I am building.
It makes sense. I use buildout for most web applications production environments, and I think many people do. It's just harder to sell if you have a sysadmin in front of you, that is used to other tools ;)
:) exactly... Regards, Martin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJLrMdnAAoJEBdvyODiyJI4hD4IAMrf8QBe1y5WeG0dK3effCPJ LrtrwsphCNhX7fEbfpmrhXB/b9tYXLBdxU1/GWrrTB/F1OukEoY1S3k76RBIN6YX beW3tr7+JFg6BvBQaZ1x+/zWCiIxLDcoCq5GYYs/HHmw+jObY7lpy+gGqRPJoUqX ubsjxXKzLKNkrQLK38KOhLDdeyRBGxfEXP2yE7G5LTO9ldKFqqPRk6L21mXK5n0V YkVEmyb9ypnlgeLwNUKMYJqH7c1XHOaAHXuddS8xUWkhzewE9eoDZQ1EO5Tto44P BxY+E8bCvgw1aFWUuj7XrE1PD8pTp+BWbgMEVWBY7FkC8uK8Tiifz4evy/YrZB4= =xXnI -----END PGP SIGNATURE-----
On Fri, Mar 26, 2010 at 3:40 PM, Martin Raspaud
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Tarek Ziadé skrev:
On Fri, Mar 26, 2010 at 3:09 PM, Martin Raspaud
wrote: [..] Packaging an entire buildout environment is not really an option I think, since we have several projects using the same eggs, and we think it would be cleaner to share them (I'm thinking especially of big eggs, like scipy and numpy).
It really depends on your needs and constraints. I had to ship full releases to customers.
In your case, you could share the same downloads and eggs folders on your productions servers maybe,
Yes, indeed.
or run your own PyPI private server to serve the archives to your buildouts when they claim it.
That looks tempting, but is it possible to have a private pypi server distributing binary (ready compiled) eggs ?
I explore these options anyway.
Yes it is possible, if you upload them to your pypi with: $ python setup.py bdist_egg register -r YOURPYPI upload -r YOURPYPY You can use chisop, eggbasket, or PloneSoftwareCenter. (and maybe others) The last one is great if you want to have a developer's website around your packages, will a lot of extra features. It's overkill if you don't need a website. That's the one in use at http://plone.org/products Regards Tarek
participants (2)
-
Martin Raspaud
-
Tarek Ziadé