So "setup.py develop" also provides the --record option, but apparently it doesn't record anything if I use it. At least it should record the creation of scripts in case there are some, but the record file results always empty. Is that the normal behaviour? I just want to make sure that I can easily clean up everything what I added to .local/bin for example.
On Fri, Nov 25, 2011 at 11:06 AM, Andrea Crotti <andrea.crotti.0@gmail.com> wrote:
So "setup.py develop" also provides the --record option, but apparently it doesn't record anything if I use it.
well, since develop just hooks a package in-place, I don't think the --record option does anything
At least it should record the creation of scripts in case there are some, but the record file results always empty. Is that the normal behaviour?
I just want to make sure that I can easily clean up everything what I added to .local/bin for example.
That's a good point. Please add a ticket here : https://bitbucket.org/tarek/distribute/issues
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
-- Tarek Ziadé | http://ziade.org
On 11/25/2011 10:32 AM, Tarek Ziadé wrote:
well, since develop just hooks a package in-place, I don't think the --record option does anything It should at least record these files for example:
Installing gen_requires.py script to /home/andrea/.local/bin Installing remove_eggs.py script to /home/andrea/.local/bin Installing dev_main_no_eggs.py script to /home/andrea/.local/bin And also the link created, which is still a file written in site-packages imho..
That's a good point. Please add a ticket here : https://bitbucket.org/tarek/distribute/issues
I will open a ticket sure, I can't rely however on the development version, so I'll need another way to fix this maybe..
Another thing which is more or less related to this. Suppose that I'm working on module a.py, which will generate a a.pyc. Now when I move a.py to b.py the a.pyc will still be there, and might make work all the imports to "a", even if they are not supposed to. Since with egg-info I can see the current sources, maybe is there a smart way to clean these unwanted pyc files?
participants (2)
-
Andrea Crotti -
Tarek Ziadé