Ez_setup py line

All the features of what can go into a setup. The contents of setup. This would be visible when someone, say, cloned your repo. In order to interact with pypi, you first need to setup an account. Now, once registered, when you run setup. To get around this, place a. The structure of a.

Do I need to install all of this, or are there parts I can leave out? Thanks, Nigel. I haven't tried enthought because I already have Python and Numpy beebn using nltk for a while. Thanks for taking the time, Cheers, N. Jurica Seva. EPD is available for Linux as well under the academic license. Enthought Python Distribution -- www. Hope this helps someone. A clean solution needs to make certain there are no more zipimporter instances with stale archive content directory caches left behind after replacing a zipped egg archive with another.

That is the method called just after the old arhive has been replaced by the new one and all the stale zipimporter instances were supposed to have been released. Following merging of Pull Request 48 , I've created to follow up with the suggestions of a more robust cache invalidation.

Big thanks to pje and jurko for all the help on this issue! Original comment by languitar Bitbucket: languitar , GitHub: languitar :. What is the state of this issue with respect to released versions of setuptools? In which version is the fix included? It was fixed in 3. See the history for other details about released versions.

Skip to content. Star 1. New issue. Jump to bottom. Labels bug minor. Copy link. Here are some of the collected test results:! See the error message above. Original comment by jaraco Bitbucket: jaraco , GitHub: jaraco : I've had this same issue. Original comment by johnsmith Bitbucket: johnsmith , GitHub: johnsmith : pje How do I remove the corresponding entry in the zipimport cache?

Original comment by jurko Bitbucket: jurko , GitHub: jurko : Have you looked at zipimport. It seems to be a dictionary with zip file paths as keys. It may be incomplete, incorrect or include features that are considered implementation detail and may vary between Python implementations. When in doubt, consult the module reference at the location listed above.

It's a subclass of ImportError, so it can be caught as ImportError, too. It is usually not needed to use the zipimport module explicitly; it is used by the builtin import mechanism for sys. Original comment by pje Bitbucket: pje , GitHub: pje : That's one cache. Original comment by jurko Bitbucket: jurko , GitHub: jurko : When I ran into it and saw no one else reported it already, and that it must have been present for a long time now, I assumed it is not all that important Original comment by pje Bitbucket: pje , GitHub: pje : Does it make a difference what Python version is used?

Original comment by jurko Bitbucket: jurko , GitHub: jurko : Ok, just tested it and the described scenario fails consistently with: CPython 2. I'll do more research on the original ZipImportError issue tomorrow. Original comment by jurko Bitbucket: jurko , GitHub: jurko : Just did some bisecting over the old repo commits, and the problematic commit has been found on the setuptools Original comment by jurko Bitbucket: jurko , GitHub: jurko : pje - I've been debugging the issue using pdb and so far I think your cleanup hook is getting called correctly.

I'll some more debugging tonight and hopefully have some more exact results for you. Original comment by pje Bitbucket: pje , GitHub: pje : Based on that commit, it looks as though the problem was exposed because of the addition of a requirements file to setuptools' metadata. Original comment by jurko Bitbucket: jurko , GitHub: jurko : Yup, that commit introduces the setuptools. Original comment by jurko Bitbucket: jurko , GitHub: jurko : I found time to do some more debugging and I can now confirm that the reason is in fact an old zipimporter instance being used to load data.

Original comment by jurko Bitbucket: jurko , GitHub: jurko : Here's some more info I'll see how to implement this cleanly and hopefully have a patch for you soon. Original comment by jurko Bitbucket: jurko , GitHub: jurko : I have prepared some debugging code that uses the CPython garbage collector to detect and report remaining stale zipimport.

Hope this helps. Original comment by pje Bitbucket: pje , GitHub: pje : Actively removing them from the environments sounds like a good idea.

Replacing a distribution in a working set is trickier than removing it from an Environment, though: you have to do something like: if ws. I hope to look into the suggested cleaner solution soon Original comment by jurko Bitbucket: jurko , GitHub: jurko : Why sorry? Original comment by jaraco Bitbucket: jaraco , GitHub: jaraco : zipimporters cache their zip archive directory information, do so as a performance optimization and provide no official way to clear this cache If that's true, and that blocks this issue, I suggest: File a ticket upstream CPython with this defect.

Push for a fix in the upstream implementation. Backport the fix into a third party library. Have setuptools use that library if it's available or fail with a nicer error message if not.

Original comment by jurko Bitbucket: jurko , GitHub: jurko : As for the upstream ticket - I have a feeling no one is actively maintaining the zipimport. Original comment by jurko Bitbucket: jurko , GitHub: jurko : An updated zipimport module implementation would allow us to use importlib. Original comment by jaraco Bitbucket: jaraco , GitHub: jaraco : Following merging of Pull Request 48 , I've created to follow up with the suggestions of a more robust cache invalidation.

Original comment by jaraco Bitbucket: jaraco , GitHub: jaraco : Big thanks to pje and jurko for all the help on this issue! Original comment by languitar Bitbucket: languitar , GitHub: languitar : What is the state of this issue with respect to released versions of setuptools? Nader Emami wrote: L. Either rename your local one or take your home folder off the Python path TJG How can do the second solution, take off the home from Python path?

Depends on your setup. There are other more obscure possibilities to do with things set in site. Keep copying to the list, please. Copying back to the list. Paul Boddie.