PYTHON 3.4 LEFTOVERS

[Ned Batchelder]

On Sunday, November 17, 2013 7:30:03 AM UTC-5, YBM wrote:
> Le 17.11.2013 10:12, Nikos a écrit :
> > Στις 16/11/2013 6:46 μμ, ο/η YBM έγραψε:
> >> Le 16.11.2013 17:30, Ferrous Cranus a écrit :
> >>> Mark wrote:
> >>>
> >>>> If you have to deliberately post like this in an attempt to annoy
> >>>> people, would you please not do so using double spaced google crap as
> >>>> it's very annoying, thank you in anticipation.
> >>>
> >>> Sure thing Mark, here:
> >>>
> >>> root at secure [~]# find / -name python3.4 | rm -rf
> >>>
> >>> root at secure [~]# locate python3.4
> >>> /root/.local/lib/python3.4
> >>> /usr/local/include/python3.4m
> >>> /usr/local/lib/libpython3.4m.a
> >>> /usr/local/lib/python3.4
> >>> /usr/local/share/man/man1/python3.4.1
> >>>
> >>> still there!!!
> >>
> >> You are utterly stupid:
> >>
> >> 1st: rm does not read its standard input so doing
> >> whatever | rm -fr is useless
> >>
> >> 2st: even if it had worked (i.e. removed the files) they
> >> would still appear with locate, as locate is just reading
> >> a database build every day by updatedb (using find btw)
> >>
> >> What you want to do can be done this way :
> >>
> >> find / -name python3.4 -exec rm -rf {} \;
> >
> > 'find / -name python34 | xargs -rf' does what i need it do
> 
> certainly not with xargs -rf, but with xargs rm -rf
> 
> > it works similar to find's built-in exec method using as argument
> > whatever matches results to.
> >
> > find / -name python3.4 -exec rm -rf {}
> >
> > So both have same effect i assume.
> 
> Yes, but they were no xargs in the command lines you wrote
> originally, Nikos.
> 
> bla bla | rm ...
> is not the same as
> bla bla | xargs rm ...
> 
> do you suffer of some kind of visual illness?


YBM: I'm going to politely ask you again to please stop.

1) Don't answer off-topic questions here.  It only encourages more off-topic questions.

2) Don't be abusive.  http://www.python.org/psf/codeofconduct/

3) Lastly, your abuse is in the form of a (rhetorical) question, which is likely to simply cause another answer, which we don't want.

Thanks, please do what you can to make this community the kind that you want.

--Ned.