[issue12405] packaging does not record/remove directories it creates

Éric Araujo added the comment: Obsolete for distutils2, but something to keep in mind for RECORD 2.0 or its successor. -- nosy: +ncoghlan resolution: -> out of date stage: -> committed/rejected status: open -> closed ___ Python tracker

[issue12405] packaging does not record/remove directories it creates

Carl Meyer added the comment: > This is what I proposed earlier: we’d need to record all directories that > would have been created, but I’m not sure if it will be possible. For > example, if one uses --prefix /tmp/usr and pysetup install creates /tmp/usr, > /tmp/usr/lib, /tmp/usr/lib/python

[issue12405] packaging does not record/remove directories it creates

Éric Araujo added the comment: [Vinay] > I think you mean "Only the paste/util directory is recorded." Obviously :) > How about if you record all directories that you would create if they didn't > exist, as well > as those actually created? That way, you would record the paste directory > und

[issue12405] packaging does not record/remove directories it creates

Carl Meyer added the comment: > Carl: Can you tell us how pip removes directories? In short - pip would _love_ to have directories recorded as well as files, exactly as Vinay has proposed. We don't have that info (even the distutils --record option currently doesn't record directories, thus i

[issue12405] packaging does not record/remove directories it creates

Vinay Sajip added the comment: > Let me rephrase my example with real paths. Okay, now I see what you're getting at. > Python creates /usr/lib/python3.3/site-packages.  (I’ll call this $stdlib.) > > pysetup3.3 install paste.script creates $stdlib/paste/script/ and files > therein.  The paste

[issue12405] packaging does not record/remove directories it creates

Éric Araujo added the comment: Let me rephrase my example with real paths. Python creates /usr/lib/python3.3/site-packages. (I’ll call this $stdlib.) pysetup3.3 install paste.script creates $stdlib/paste/script/ and files therein. The paste and paste/script directories are recorded. pysetu

[issue12405] packaging does not record/remove directories it creates

Vinay Sajip added the comment: > I did not propose such a thing. Sorry, I misunderstood your reference to /usr/lib/python2.7/site-packages. -- ___ Python tracker ___ __

[issue12405] packaging does not record/remove directories it creates

Éric Araujo added the comment: > IMO there is no need to remember any directory which isn't actually > created by pysetup3 I did not propose such a thing. -- ___ Python tracker ___

[issue12405] packaging does not record/remove directories it creates

Vinay Sajip added the comment: >s/directory that existed before Python was installed/directory that existed >before any distribution was installed/ IMO there is no need to remember any directory which isn't actually created by pysetup3. Deleting a __pycache__ in a directory created by pysetup

[issue12405] packaging does not record/remove directories it creates

Éric Araujo added the comment: s/directory that existed before Python was installed/directory that existed before any distribution was installed/ -- ___ Python tracker ___

[issue12405] packaging does not record/remove directories it creates

Éric Araujo added the comment: > I'm not sure what you mean by "using". AFAIK, each distribution's files > (recorded in RECORD) > would be unique to that distribution (else distros like Debian will have > problems, since > files are owned by one package and one package only). Files need to bel

[issue12405] packaging does not record/remove directories it creates

Vinay Sajip added the comment: s/dependencies between dependencies/dependencies between distributions/ -- ___ Python tracker ___ ___

[issue12405] packaging does not record/remove directories it creates

Vinay Sajip added the comment: > If one project creates a/b/thing and another project uses > a/b/otherthing, then the directories would be recorded in the first > project’s RECORD, but they should be removed only when both projects > are removed. I'm not sure what you mean by "using". AFAIK, ea

[issue12405] packaging does not record/remove directories it creates

Éric Araujo added the comment: If one project creates a/b/thing and another project uses a/b/otherthing, then the directories would be recorded in the first project’s RECORD, but they should be removed only when both projects are removed. -- ___ Py

[issue12405] packaging does not record/remove directories it creates

Vinay Sajip added the comment: > I share that opinion.  So, the first step would be to record created > directories.  We could extend PEP 376 and write entries without hash nor > length > record for directories in RECORD, or use another file in the dist-info dir. IMO using RECORD would be p

[issue12405] packaging does not record/remove directories it creates

Éric Araujo added the comment: > IMO in this situation, a and b were created by the installation and so > should be removed, unless they contain files not added during installation. I share that opinion. So, the first step would be to record created directories. We could extend PEP 376 and w

[issue12405] packaging does not record/remove directories it creates

Vinay Sajip added the comment: More info on the problem (not Windows specific): if the installation creates a file several levels down a/b/c/file then during removal, only a/b/c is regarded as a candidate for removal; a/b and a are not considered as deletion candidates, and so never deleted,

[issue12405] packaging does not record/remove directories it creates

Vinay Sajip added the comment: I see that there's code to do this in install.py, but for some reason it seems not to be working in Windows. Investigating. -- ___ Python tracker ___

[issue12405] packaging does not record/remove directories it creates

New submission from Vinay Sajip : pysetup3 install should not only record files that it installs, but also any directories it creates. pysetup3 remove should then delete those directories (if empty after removing their installed contents). -- assignee: tarek components: Distutils2, Lib