On Dec 15, 2:04 am, "Edward K. Ream" <[email protected]> wrote:
> Hmm. I would have thought that bzr would remove .pyc when removing > corresponding .py files. If not, this would be a pretty bad bzr > glitch. You seem to be expecting too much of bzr. Bzr is configured to ignore .pyc files, so it simply and always ignores them. In the following example I make a new bzr repository, I source control test1.py, I generate test1.pyc, I use bzr to move test1.py, test1.pyc is left undisturbed: 19:34:53 ~$ mkdir bzrPyc 19:34:59 ~$ cd bzrPyc 19:35:03 ~/bzrPyc$ bzr init Created a standalone tree (format: 2a) 19:35:15 ~/bzrPyc$ bzr add . 19:35:25 ~/bzrPyc$ bzr status 19:35:30 ~/bzrPyc$ bzr add test1.py adding test1.py 19:36:48 ~/bzrPyc$ bzr commit -m 'Project to determine what Bazaar does with .pyc when a .py file is moved or deleted.' Committing to: /home/bob/ bzrPyc/ added test1.py Committed revision 1. 19:41:58 ~/bzrPyc$ python Python 2.7.2+ (default, Oct 4 2011, 20:03:08) [GCC 4.6.1] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import test1 >>> exit() 19:42:55 ~/bzrPyc$ bzr mkdir trunk added trunk 19:43:31 ~/bzrPyc$ bzr mv test1.py trunk test1.py => trunk/test1.py 19:43:43 ~/bzrPyc$ python Python 2.7.2+ (default, Oct 4 2011, 20:03:08) [GCC 4.6.1] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import test1 >>> exit() 19:45:01 ~/bzrPyc$ -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
