[PyChecker-list] =?ISO-2022-JP?B?GyRCM1AkKCRGJCQkXiQ5JCshKSEpGyhC?=

[<nakano_miho@au...>]

覚えてますか？？
とは言ってももうだいぶ前の事だから覚えてる訳がないよね・・・。
忘れちゃったかもしれないけど聞いてもらえるかな。
あの時、あなたが私に言ってくれた事、それがずっと頭のすみっこに残ってて・・・あの時いきなり連絡を途切ったのは私で、
言い訳にしかならないけどちょっとしたゴタゴタで連絡できなくなってしまって。
実は結構前から連絡はできる状態だったんだけど今更連絡するのはいけないことかと思ったんですが、もう一度あなたと
前みたいに話がしたくて・・・会いたくて今返事を出しました。
もし、まだ良いといってくれるなら返事ください。今更勝手いってすいません。
 
☆(*＾-＾*)＾-＾*)☆☆(*＾-＾*)＾-＾*)☆
なかの みほ　（MIHO NAKANO)
nakano_miho@...
☆(*＾-＾*)＾-＾*)☆☆(*＾-＾*)＾-＾*)☆ 

Re: [PyChecker-list] Pychecker Bug Summary

[Kenneth Pronovici <pronovic@sk...>]

On Tue, Mar 22, 2005 at 12:13:40PM -0600, Kenneth Pronovici wrote:
> These are all of the bugs that I have looked at in detail at this point.
> The free time I had available to me is beginning to run out for now,
> but as I look at more bugs, I'll get you a similar summary.

I have now also submitted patches with potential fixes for these
additional bugs:

   856597
   888645
   1021052

There are also some additional notes at for these bugs:

   1116168
   1166658

Plus, I noticed a few other bugs that seem to be duplicates of the stack
problem.  These bug numbers are now noted in the existing reports I
pointed you to originally.

KEN

-- 
Kenneth J. Pronovici <pronovic@...>

[PyChecker-list] Online Drugs - save up to 80%

[Douglas Clements <douglas.clements_94@vi...>]

Online pharmacy - Visit our online store and save.

Save up to 80% compared to normal rates.

All popular drugs are available!

- World wide shipping
- No Doctor Visits
- No Prescriptions
- Next Day Priority Shipping
- Discreet Packaging
- Buy in Bulk and Save!

We make it easier and faster than ever to get the prescriptions you
need.

Go here: http://jomr.com/



Simply Rx is your convenient, safe and private online source for
FDA approved pharmacy prescriptions. We sell brand-name and exact
generic equivalents of US FDA approved prescription drugs through
our fully-licensed overseas pharmacy. Upon approval of your medical
information, a licensed physician will issue a free prescription
which can be filled and shipped to you in one business day.


No thanks: http://jomr.com/z.php

[PyChecker-list] Pychecker Bug Summary

[Kenneth Pronovici <pronovic@sk...>]

Neal,=20

Here is my first report on bugs that I have looked at.  I have tried to
group related bugs together into sets that you (or someone) should look
at all at once to get the most benefit out of the research I've done.

The following bugs have been documented by you or someone else
as something that won't be fixed.  Most haven't had any activity for
a while.  I guess you could consider closing them:

   534737
   562403
   583069

I have submitted fixes and/or patches for the following bugs:

   920966
   968726
   1004761
   1093311
   1094871

I believe that the following reports do not really represent bugs.  They
are either enhancement requests or are caused by misunderstandings about
how pychecker works:

   851570
   882359
   1098697
   1042776
   1058116
   1092224

I consider all of the following bugs unreproducible:

   516743
   524370
   555771
   566779
   571549
   585040
   598732
   602673
   613298
   708546
   765900
   896388
   924693
   1023843
   1086120
   1116165

I have noticed that quite a few of the remaining open bugs seem to
involve deeply nested functions.  It feels to me like all of these bugs
are related, even though they manifest themselves in several different
ways.

The following bugs are all basically the same internal error caused
by an incorrect reference to co_freevars within _LOAD_DEREF().  I have
put most of my notes by #1120709.

   1120709
   1114902
   1097857
   1046442
   880101
   859007

Bug #1070854 seems to be caused by a stack-logic problem within the Code
class.  When function or method calls are nested, i.e. a(b()), the stack
logic seems to sometimes lose one of the calls.  Bug #1119311 is another
problem with the layout of the stack.  It looks like sometimes different
things get put into the stack for what should be equivalent code.  I
suspect that the other bugs are related, but I can't prove it.  I have
put most of my notes by #1070854 and #1119311.

   1119311
   1070854
   922154
   815305
   657199
   657971

These are all of the bugs that I have looked at in detail at this point.
The free time I had available to me is beginning to run out for now,
but as I look at more bugs, I'll get you a similar summary.

KEN

--=20
Kenneth J. Pronovici <pronovic@...>

[PyChecker-list] Re: Pychecker Bug Triage

[Kenneth Pronovici <pronovic@sk...>]

From: Kenneth Pronovici <pronovic@...>
To: Neal Norwitz <neal@...>,
Cc: ecn@..., pychecker-list@...
Bcc: 
Subject: Re: Pychecker Bug Triage
Reply-To: Kenneth Pronovici <pronovic@...>
In-Reply-To: <20050318144340.GI7198@...>

On Fri, Mar 18, 2005 at 09:43:40AM -0500, Neal Norwitz wrote:
> On Wed, Mar 16, 2005 at 04:47:12PM -0600, Kenneth Pronovici wrote:
> > After I get my notes into the bug tracking system, I'm going to try (as
> > time allows) to start picking off low-hanging fruit.  I'll also get you
> > to a list of bugs that I think should be closed because they can't be
> > reproduced or because Python 1.5 isn't supported any more, etc.  I won't
> > actually close any bugs or commit any code without an OK from one of
> > you.
> 
> We're both going to be pretty busy over the next couple of weeks.
> I'll try to look over everything.  Hopefully you are correct
> that many of the bugs can be closed or are duplicates.

Ok.  I assumed you would be busy, and I did not expect that you would
have time to look all of this over right away.  At some point in here I
will get you a list of specific bugs I need your opinion on, so you
don't have to slog through the entire list.

I don't seem to be able to attach anything to bug reports (should I be
able to?) so as I manage to fix things I'll submit patches and then make
a note of the patch number in the bug report.  You can them let me know
when it's OK to commit.  

Have a good weekend.

KEN

-- 
Kenneth J. Pronovici <pronovic@...>

[PyChecker-list] Re: Pychecker Bug Triage

[Neal Norwitz <neal@me...>]

On Wed, Mar 16, 2005 at 04:47:12PM -0600, Kenneth Pronovici wrote:
> Neal, Eric -
> 
> I've been working on some bug triage among the pychecker bugs.  I've
> gone through all 65 of the open bugs and where possible created real .py
> files (formatted properly and not mangled by the bug submission process)
> based on the bug reports.  I've also made notes about Python versions
> that apply, things that don't make sense about the reports, bug
> duplications, etc.
> 
> Over the course of the next few days or the next week, I'm going to
> start getting my notes into the bug tracking system on SourceForge.
> I'll also attach the test cases that I developed where needed.

Thanks.  I noticed you made many comments.

> I don't know who gets mail (if anyone) when SourceForge bugs are
> updated, but there will be a lot of it coming as I do this.  I wanted to
> give you a little warning.

I think we both get mail.  There might even be a mailing list, I don't
remember.

> After I get my notes into the bug tracking system, I'm going to try (as
> time allows) to start picking off low-hanging fruit.  I'll also get you
> to a list of bugs that I think should be closed because they can't be
> reproduced or because Python 1.5 isn't supported any more, etc.  I won't
> actually close any bugs or commit any code without an OK from one of
> you.

We're both going to be pretty busy over the next couple of weeks.
I'll try to look over everything.  Hopefully you are correct
that many of the bugs can be closed or are duplicates.

Neal

[PyChecker-list] Pychecker Bug Triage

[Kenneth Pronovici <pronovic@sk...>]

Neal, Eric -

I've been working on some bug triage among the pychecker bugs.  I've
gone through all 65 of the open bugs and where possible created real .py
files (formatted properly and not mangled by the bug submission process)
based on the bug reports.  I've also made notes about Python versions
that apply, things that don't make sense about the reports, bug
duplications, etc.

Over the course of the next few days or the next week, I'm going to
start getting my notes into the bug tracking system on SourceForge.
I'll also attach the test cases that I developed where needed.

I don't know who gets mail (if anyone) when SourceForge bugs are
updated, but there will be a lot of it coming as I do this.  I wanted to
give you a little warning.

After I get my notes into the bug tracking system, I'm going to try (as
time allows) to start picking off low-hanging fruit.  I'll also get you
to a list of bugs that I think should be closed because they can't be
reproduced or because Python 1.5 isn't supported any more, etc.  I won't
actually close any bugs or commit any code without an OK from one of
you.

Let me know if you have any questions.

KEN

--=20
Kenneth J. Pronovici <pronovic@...>

[PyChecker-list] Re: 44ETG-Pharmaaccy-98

[Joseba Frye <Ishmerai@je...>]

Hello, 

were paid and dropped--put aside and forgotten.  As for judges,
That'll be fine, won't it, Frank! she observed, and rubbed his
and pose and hold her nose up.

the true commercial and financial adjustment of the country, and
was to follow.
I'll get together with you all, later.  Just now I'd like to go
the sets of furniture put on the market for general sale by the
which was not perfectly legal, but that he must be complacent and
He, too, was thinking how useless it was for any one to approach


Have a nice day.