Comments on: PyDev note about refactoring http://ironboundsoftware.com/blog/2006/05/26/pydev-note-about-refactoring/ Droplets of Yes and No Fri, 31 Dec 2010 05:48:28 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: » Thanks! - Possibility And Probability http://ironboundsoftware.com/blog/2006/05/26/pydev-note-about-refactoring/comment-page-1/#comment-1739 » Thanks! - Possibility And Probability Mon, 29 May 2006 20:50:13 +0000 http://www.ironboundsoftware.com/blog/?p=216#comment-1739 [...] The other day I posted about problem I was having while refactoring some python code while using the Pydev plugin for Eclipse. Fabio Zadrozny (one of the developers for Pydev) saw my post and asked for some more details on my problem. After a few emails he had a work around for the issue. Thanks Fabio! [...] [...] The other day I posted about problem I was having while refactoring some python code while using the Pydev plugin for Eclipse. Fabio Zadrozny (one of the developers for Pydev) saw my post and asked for some more details on my problem. After a few emails he had a work around for the issue. Thanks Fabio! [...]

]]> By: Nick http://ironboundsoftware.com/blog/2006/05/26/pydev-note-about-refactoring/comment-page-1/#comment-1738 Nick Mon, 29 May 2006 15:18:16 +0000 http://www.ironboundsoftware.com/blog/?p=216#comment-1738 Hi Fabio, thanks for your comment! Yes, when I first wrote this posting, the pythonpath was not set. I have since set the pythonpath, but when I repeated my test it still didn't delete the pyc files. I'm sending you an email detailing what I did. -Nick Hi Fabio, thanks for your comment!

Yes, when I first wrote this posting, the pythonpath was not set. I have since set the pythonpath, but when I repeated my test it still didn’t delete the pyc files.

I’m sending you an email detailing what I did.

-Nick

]]> By: Fabio Zadrozny http://ironboundsoftware.com/blog/2006/05/26/pydev-note-about-refactoring/comment-page-1/#comment-1737 Fabio Zadrozny Mon, 29 May 2006 14:22:12 +0000 http://www.ironboundsoftware.com/blog/?p=216#comment-1737 Hi, actually, it does delete the .pyc files here... It just does not do it if your pythonpath is not correctly configured (I'd recommend checking the getting started manual to see if all is correctly configured: http://www.fabioz.com/pydev/manual_101_root.html) So, basically, .pyc files from .py files that are not found to be in the pythonpath are not erased (but otherwise they are). If you're able to reproduce this when the file is in your pythonpath, please report a bug with the details for reproducing it. Cheers, Fabio Hi, actually, it does delete the .pyc files here… It just does not do it if your pythonpath is not correctly configured (I’d recommend checking the getting started manual to see if all is correctly configured: http://www.fabioz.com/pydev/manual_101_root.html)

So, basically, .pyc files from .py files that are not found to be in the pythonpath are not erased (but otherwise they are).

If you’re able to reproduce this when the file is in your pythonpath, please report a bug with the details for reproducing it.

Cheers,

Fabio

]]> By: Nick http://ironboundsoftware.com/blog/2006/05/26/pydev-note-about-refactoring/comment-page-1/#comment-1736 Nick Sat, 27 May 2006 16:45:14 +0000 http://www.ironboundsoftware.com/blog/?p=216#comment-1736 Yeah, I'm "once bitten, twice shy" when it comes to messing with good code. I like the benefits of refactoring, but I've got to have that warm and fuzzy that everything still works. I hear you about the code rot, I'm not sure what my timeline is though. I would guess around 6 months or so. I think a lot of it also depends on how many other projects I'm working on at the same time. :) That's why I've always been big on comments, and I'm now become big on tests. One thing to describe the intent, another to test it. -Nick Yeah, I’m “once bitten, twice shy” when it comes to messing with good code. I like the benefits of refactoring, but I’ve got to have that warm and fuzzy that everything still works.

I hear you about the code rot, I’m not sure what my timeline is though. I would guess around 6 months or so. I think a lot of it also depends on how many other projects I’m working on at the same time. :) That’s why I’ve always been big on comments, and I’m now become big on tests. One thing to describe the intent, another to test it.

-Nick

]]> By: jerry chen http://ironboundsoftware.com/blog/2006/05/26/pydev-note-about-refactoring/comment-page-1/#comment-1735 jerry chen Sat, 27 May 2006 05:37:36 +0000 http://www.ironboundsoftware.com/blog/?p=216#comment-1735 how very observant and careful of you. it is of utmost importance to maintain a healthy amount of skepticism that the code is "okay". ignorance is not bliss. just because it runs today doesn't mean it will run tomorrow! i constantly code review my stuff on printouts to make sure the logic is consistent (maybe not so healthy, but i'm not burdened with deadlines, yet). i don't know about you, but to me, code seems to decay with time. as i develop better coding practices, or different styles, old code that seemed to run fine at one time look absolutely horrible now. my average code decay rate is 4 months from fresh to rot, it has steadied a bit in recent years. of course, it's a different story with unit tests. however, it is still possible to subconsciously forge "convenient" and "easy" special case tests and be complacent and overly optimistic about things. how very observant and careful of you. it is of utmost importance to maintain a healthy amount of skepticism that the code is “okay”. ignorance is not bliss. just because it runs today doesn’t mean it will run tomorrow! i constantly code review my stuff on printouts to make sure the logic is consistent (maybe not so healthy, but i’m not burdened with deadlines, yet).

i don’t know about you, but to me, code seems to decay with time. as i develop better coding practices, or different styles, old code that seemed to run fine at one time look absolutely horrible now. my average code decay rate is 4 months from fresh to rot, it has steadied a bit in recent years.

of course, it’s a different story with unit tests. however, it is still possible to subconsciously forge “convenient” and “easy” special case tests and be complacent and overly optimistic about things.

]]>