Python setup.py bdist_egg

It also provides a way to create Python eggs. Let's spend a little time getting to know this utility. Here's a sample invocation:. So if you install something complex, like TurboGears, you'll see it install lots of packages. This is one reason why you may want to use virtualenv in that you can make sure you like the new packages and that they work correctly. If they don't, you just delete the virtualenv folder. Otherwise you'll have to go into your Python folder and dig around and try to "uninstall" i.

Fortunately you can use pip to uninstall it for you if you don't like to do all that fiddling yourself. It shouldn't break the way it's done now. I completely agree. I find it very strange that there is no option to select a different output folder AND that the clean command does not really remove the generated artifacts.

I think a out-of-source build and proper clean should be natively supported by setuptools, as per previous comments. In my case I just build a source distribution with no data files, extensions etc, just plain python archive. I found a workaround for this issue - having workdir at repo root as usual, use command: python setup. Like others who've commented here, I have had to resort to a custom clean command to remove the dist directory. It would be good if this could be fixed in setuptools.

A user would reasonably expect that python setup. However, I haven't come across a situation where I want a partial clean so I'm not sure there is much point in a --all flag: clean should just clean everything. Skip to content. Star 1. New issue. Jump to bottom. Labels Needs Triage. Enter search terms or a module, class or function name. Getting Started With setuptools and setup. This tutorial will focus on the bare minimum basics you need to get setuptools running so you can: Register your package on pypi.

Setting up setup. Using setup. Note A key point here is you need to run these commands with the version of python you want to support. Created using Sphinx 0. Keep in mind, however, that the egg runtime system expects to see eggs with distutils platform names, so it may ignore or reject eggs with non-standard platform names.

Similarly, the EasyInstall program may ignore them when searching web pages for download links. However, if you are cross-compiling or doing some other unusual things, you might find a use for this option. There are also some options you will probably never need, but which are there because they were copied from similar bdist commands used as an example for creating this one.

They may be useful for testing and debugging, however, which is why we kept them:. Keep the contents of the --bdist-dir tree around after creating the. Set the temporary directory for creating the distribution. The entire contents of this directory are zipped to create the. This deployment is done in such a way that changes to the project source are immediately available in the staging area s , without needing to run a build or install step after each change.

The develop command works by creating an. And, it ensures that any missing project dependencies are available in the staging area, by downloading and installing them if necessary.

Most other kinds of changes to your project should not require any build operations or rerunning develop , but keep in mind that even minor changes to the setup script e.

Here are some of the options that the develop command accepts. Un-deploy the current project. You may use the --install-dir or -d option to designate the staging area. The created. The project directory will be removed from easy-install.

Note that this option currently does not uninstall script wrappers! You must uninstall them yourself, or overwrite them by using pip to install a different version of the package. You can also avoid installing script wrappers in the first place, if you use the --exclude-scripts aka -x option when you run develop to deploy the project.

Specifying this option prevents develop from adding an easy-install. In which case the wrapper script calls require for you. Note that if you install to a directory other than site-packages , this option is automatically in effect, because.

So, if you use the --install-dir or -d option or they are set via configuration file s your project and its dependencies will be deployed in multi- version mode.