I am using some packages in python3.2 which create a __pycache__ folder. These
folders is routinely blocking my updates and I have to remove the folders
manually. Are any other among you facing the same problem? If yes, can I
automatize it somehow?
Thanks
--
Regards
Jayesh Badwaik
stop html mail | always bottom-post
www.asciiribbon.org | www.netmeister.org/news/learn2quote.html
05-08-2012, 09:07 PM
martin kalcher
Clearing __pycache__ folders
Am 08.05.2012 22:21, schrieb Jayesh Badwaik:
Hi,
I am using some packages in python3.2 which create a __pycache__ folder. These
folders is routinely blocking my updates and I have to remove the folders
manually. Are any other among you facing the same problem? If yes, can I
automatize it somehow?
Thanks
Hey,
these pycache folders *should* be created with a python setup script
[0], which *should* be called in the PKGBUILD during buildtime, so they
*should* be part of the package. If not, python creates them during
runtime and messes up your system...
So the cleanest way is to write a setup script and send it to the
maintainer.
The quicker way is to write a simple script, the checks your file system
for disowned files. See: [1]
[0] http://docs.python.org/py3k/distutils/setupscript.html
[1]
https://wiki.archlinux.org/index.php/Pacman_Tips#Identify_files_not_owned_by_any_packag e
05-08-2012, 09:13 PM
martin kalcher
Clearing __pycache__ folders
Am 08.05.2012 23:07, schrieb martin kalcher:
Am 08.05.2012 22:21, schrieb Jayesh Badwaik:
Hi,
I am using some packages in python3.2 which create a __pycache__
folder. These
folders is routinely blocking my updates and I have to remove the folders
manually. Are any other among you facing the same problem? If yes, can I
automatize it somehow?
Thanks
Hey,
these pycache folders *should* be created with a python setup script
[0], which *should* be called in the PKGBUILD during buildtime, so they
*should* be part of the package. If not, python creates them during
runtime and messes up your system...
So the cleanest way is to write a setup script and send it to the
maintainer.
The quicker way is to write a simple script, the checks your file system
for disowned files. See: [1]
[0] http://docs.python.org/py3k/distutils/setupscript.html
[1]
https://wiki.archlinux.org/index.php/Pacman_Tips#Identify_files_not_owned_by_any_packag e
Or use pacmans -f switch to overwrite them.
Cheers, ushi
05-09-2012, 12:58 AM
Oon-Ee Ng
Clearing __pycache__ folders
On Wed, May 9, 2012 at 5:13 AM, martin kalcher
<martin.kalcher@googlemail.com> wrote:
> Am 08.05.2012 23:07, schrieb martin kalcher:
>
>> Am 08.05.2012 22:21, schrieb Jayesh Badwaik:
>>>
>>> Hi,
>>>
>>> I am using some packages in python3.2 which create a __pycache__
>>> folder. These
>>> folders is routinely blocking my updates and I have to remove the folders
>>> manually. Are any other among you facing the same problem? If yes, can I
>>> automatize it somehow?
>>>
>>> Thanks
>>
>>
>> Hey,
>>
>> these pycache folders *should* be created with a python setup script
>> [0], which *should* be called in the PKGBUILD during buildtime, so they
>> *should* be part of the package. If not, python creates them during
>> runtime and messes up your system...
>>
>> So the cleanest way is to write a setup script and send it to the
>> maintainer.
>>
>> The quicker way is to write a simple script, the checks your file system
>> for disowned files. See: [1]
>>
>> [0] http://docs.python.org/py3k/distutils/setupscript.html
>> [1]
>>
>> https://wiki.archlinux.org/index.php/Pacman_Tips#Identify_files_not_owned_by_any_packag e
>>
>
> Or use pacmans -f switch to overwrite them.
>
> Cheers, ushi
If, of course you know what you're doing. -f can do *bad things* otherwise....
05-09-2012, 03:54 AM
Jayesh Badwaik
Clearing __pycache__ folders
On Tuesday 08 May 2012 23:13:54 martin kalcher wrote:
> > Hey,
> >
> > these pycache folders *should* be created with a python setup script
> > [0], which *should* be called in the PKGBUILD during buildtime, so they
> > *should* be part of the package. If not, python creates them during
> > runtime and messes up your system...
> >
> > So the cleanest way is to write a setup script and send it to the
> > maintainer.
> >
> > The quicker way is to write a simple script, the checks your file system
> > for disowned files. See: [1]
> >
> > [0] http://docs.python.org/py3k/distutils/setupscript.html
> > [1]
> > https://wiki.archlinux.org/index.php/Pacman_Tips#Identify_files_not_owned_
> > by_any_package
> Or use pacmans -f switch to overwrite them.
>
> Cheers, ushi
Thanks for the clarification. I would try to write a script for the package and
send it to the maintainer.
pacman -f seems a bad option. It seems hazardous to make it a habit. :-(
--
Cheers and Regards
Jayesh Badwaik
stop html mail | always bottom-post
www.asciiribbon.org | www.netmeister.org/news/learn2quote.html