Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #37250 > unrolled thread

pycache directories

Back to article view | Back to comp.lang.python

Contents

  pycache directories monosij.forums@gmail.com - 2013-01-21 20:55 -0800
    Re: pycache directories Terry Reedy <tjreedy@udel.edu> - 2013-01-22 01:01 -0500
      Re: pycache directories monosij.forums@gmail.com - 2013-01-22 15:44 -0800
      Re: pycache directories monosij.forums@gmail.com - 2013-01-22 15:44 -0800
    Re: pycache directories jorvis@gmail.com - 2013-05-03 11:54 -0700

#37250 — pycache directories

I am doing some OO python3 where I am using multiple dirs/sub-dirs.

So everything works fine, however when I run code __pycache__ directories are being created in every directory touched by the execution.

Is it possible to set a configuration to be able to create these pycache directories in a specific location?

Coming from the Java world - am used to the /src, /bin aspects - so somewhat prefer the 'executables' out of the way.

I am using python3 on Ubuntu so wondering if there is some environ setting?

Thanks for your help.

[toc] | [next] | [standalone]

#37251

On 1/21/2013 11:55 PM, monosij.forums@gmail.com wrote:
> I am doing some OO python3 where I am using multiple dirs/sub-dirs.
>
> So everything works fine, however when I run code __pycache__
> directories are being created in every directory touched by the
> execution.

This is much better than having multiple .pyc files in every directory, 
as in Py2. You should soon learn to ignore them.

> Is it possible to set a configuration to be able to create these
> pycache directories in a specific location?

No. (I am very sure.) You can however, not have the .pyc files written, 
but that means recompile with every run. So that option is meant for 
running off a read-only medium.

-- 
Terry Jan Reedy

[toc] | [prev] | [next] | [standalone]

#37359

On Tuesday, January 22, 2013 1:01:44 AM UTC-5, Terry Reedy wrote:
> 
> > I am doing some OO python3 where I am using multiple dirs/sub-dirs.
> 
> >
> 
> > So everything works fine, however when I run code __pycache__
> 
> > directories are being created in every directory touched by the
> 
> > execution.
> 
> 
> 
> This is much better than having multiple .pyc files in every directory, 
> 
> as in Py2. You should soon learn to ignore them.
> 
> 
> 
> > Is it possible to set a configuration to be able to create these
> 
> > pycache directories in a specific location?
> 
> 
> 
> No. (I am very sure.) You can however, not have the .pyc files written, 
> 
> but that means recompile with every run. So that option is meant for 
> 
> running off a read-only medium.
> 
> 
> 
> -- 
> 
> Terry Jan Reedy

Thanks Terry. I understand needing to adjust.
Appreciate this forum.

Monosij

[toc] | [prev] | [next] | [standalone]

#37383

On Tuesday, January 22, 2013 1:01:44 AM UTC-5, Terry Reedy wrote:
> 
> > I am doing some OO python3 where I am using multiple dirs/sub-dirs.
> 
> >
> 
> > So everything works fine, however when I run code __pycache__
> 
> > directories are being created in every directory touched by the
> 
> > execution.
> 
> 
> 
> This is much better than having multiple .pyc files in every directory, 
> 
> as in Py2. You should soon learn to ignore them.
> 
> 
> 
> > Is it possible to set a configuration to be able to create these
> 
> > pycache directories in a specific location?
> 
> 
> 
> No. (I am very sure.) You can however, not have the .pyc files written, 
> 
> but that means recompile with every run. So that option is meant for 
> 
> running off a read-only medium.
> 
> 
> 
> -- 
> 
> Terry Jan Reedy

Thanks Terry. I understand needing to adjust.
Appreciate this forum.

Monosij

[toc] | [prev] | [next] | [standalone]

#44681

I agree, this would be a good feature.  I redirect my emacs backups to a single directory too so that they're not distributed all over the file system.  While I don't know how to do that with the things python creates, I've read a few ways you can disable their creation altogether (assuming you don't care or need the benefit of their use):

You can run python with -B or set the environmental variable PYTHONDONTWRITEBYTECODE=1

For fun, lots of developer discussion about its original creation here:

http://www.gossamer-threads.com/lists/python/dev/815510

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web