From internationalsales at targetstandards.com Thu Nov 1 21:43:10 2007 From: internationalsales at targetstandards.com (nec-2008) Date: Thu, 1 Nov 2007 17:43:10 -0300 Subject: [spambayes-dev] NEC-2008 - National Electrical Code 2008 / 864 pages, Download now Message-ID: <1850624-220071141204310741@Notetarget-06> An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/spambayes-dev/attachments/20071101/bf3bff71/attachment.htm From skip at pobox.com Wed Nov 7 03:21:19 2007 From: skip at pobox.com (skip at pobox.com) Date: Tue, 6 Nov 2007 20:21:19 -0600 Subject: [spambayes-dev] Feedback requested on an external lockfile module... Message-ID: <18225.8479.889051.141827@montanaro.dyndns.org> All this business about safely writing pickles got me to wondering about locking files. Rather than implement something which was SpamBayes-specific, I scouted around a little bit then implemented something which hopefully * has a reasonable API (I think) * is cross-platform * allows multiple different implementations (currently one each based on os.link and os.mkdir and one which uses a SQLite database to maintain lock info) * might someday be good enough for inclusion in Python proper as the One True Way to do advisory file locking. The result is the lockfile module, which you can find at your local neighborhood (virtual) cheese shop: http://pypi.python.org/pypi/lockfile/ I've done a fair amount of testing on my Mac. (It has a fair number of doctests. Thank you again Uncle Timmy.) Scott Dial (from the python-dev mailing list) ran it through its paces on Windows a bit and sent me some revisions. Other than Scott's inputs I've received no direct feedback on the module, though when I first raised the idea of one-lock-mechanism-to- rule-them-all it generated a few comments. I suspect Py3k and an impending 2.5.2 release are probably sucking up all available Python developer round tuits. Today I added lockfile usage into Dave Abrahams' safe_pickle function, in the process renaming it to safe_pickle_write and adding a corresponding safe_pickle_read. I then replaced all pickle.{dump,load} calls with the relevant safe_pickle_{write,read} functions. This code has not been checked in yet. I've attached a diff against the current rev 3168. I'm interested in how people think I should proceed. Some possibilities: * throw it out - we don't need dependencies on external crap * keep it but pull lockfile into the spambayes package for ease of distribution * check the changes in on head * create a branch and check the changes in there * get 1.1 out the door, damn it! leave this for 1.2 (around 2011) * keep the safe_pickle_{read,write} functions but take out the lockfile stuff. Feedback please. Thx, Skip -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: spamlock.diff Url: http://mail.python.org/pipermail/spambayes-dev/attachments/20071106/2e9e0d54/attachment.txt From skip at pobox.com Wed Nov 7 04:15:03 2007 From: skip at pobox.com (skip at pobox.com) Date: Tue, 6 Nov 2007 21:15:03 -0600 Subject: [spambayes-dev] Update PyPI entry for SpamBayes? Message-ID: <18225.11703.67003.488335@montanaro.dyndns.org> It seems that the SpamBayes entry in PyPI is a bit outdated. It still lists 1.1a2: http://pypi.python.org/pypi/spambayes/ Anyone got a few minutes to either update the entry or add me as an owner? Currently Anthony, Tony, Mark and Richie are listed. Thx, Skip From dave at boost-consulting.com Wed Nov 7 23:34:10 2007 From: dave at boost-consulting.com (David Abrahams) Date: Wed, 07 Nov 2007 17:34:10 -0500 Subject: [spambayes-dev] Feedback requested on an external lockfile module... References: <18225.8479.889051.141827@montanaro.dyndns.org> Message-ID: <874pfxy9b1.fsf@grogan.peloton> on Tue Nov 06 2007, skip-e+AXbWqSrlAAvxtiuMwx3w-AT-public.gmane.org wrote: > Today I added lockfile usage into Dave Abrahams' safe_pickle function, in > the process renaming it to safe_pickle_write and adding a corresponding > safe_pickle_read. I then replaced all pickle.{dump,load} calls with the > relevant safe_pickle_{write,read} functions. > > This code has not been checked in yet. I've attached a diff against the > current rev 3168. I'm interested in how people think I should proceed. > Some possibilities: > > * throw it out - we don't need dependencies on external crap > * keep it but pull lockfile into the spambayes package for ease of > distribution > * check the changes in on head > * create a branch and check the changes in there > * get 1.1 out the door, damn it! leave this for 1.2 (around 2011) > * keep the safe_pickle_{read,write} functions but take out the lockfile > stuff. > > Feedback please. I'm not really in a position to comment on how this package ought to evolve w.r.t. SpamBayes, but I want to express my gratitude for your attention to "handling the problem right," and my support for immediately including in SpamBayes some form of concurrent read/write protection that's at least as capable as my patch. Thanks a lot for spending time on this, -- Dave Abrahams Boost Consulting http://www.boost-consulting.com From mhammond at skippinet.com.au Thu Nov 8 01:19:22 2007 From: mhammond at skippinet.com.au (Mark Hammond) Date: Thu, 8 Nov 2007 11:19:22 +1100 Subject: [spambayes-dev] Feedback requested on an external lockfile module... In-Reply-To: <18225.8479.889051.141827@montanaro.dyndns.org> References: <18225.8479.889051.141827@montanaro.dyndns.org> Message-ID: <03dc01c8219d$13c1f700$3b45e500$@com.au> > All this business about safely writing pickles got me to wondering > about locking files. Rather than implement something which was > SpamBayes-specific, I scouted around a little bit then implemented > something which hopefully > > * has a reasonable API (I think) > * is cross-platform > * allows multiple different implementations (currently one each based > on > os.link and os.mkdir and one which uses a SQLite database to > maintain > lock info) > * might someday be good enough for inclusion in Python proper as the > One > True Way to do advisory file locking. > > The result is the lockfile module, which you can find at your local > neighborhood (virtual) cheese shop: > > http://pypi.python.org/pypi/lockfile/ > > I've done a fair amount of testing on my Mac. (It has a fair number of > doctests. Thank you again Uncle Timmy.) Scott Dial (from the python- > dev mailing list) ran it through its paces on Windows a bit and sent me > some revisions. Other than Scott's inputs I've received no direct > feedback on the module, though when I first raised the idea of one- > lock-mechanism-to- rule-them-all it generated a few comments. I > suspect Py3k and an impending > 2.5.2 release are probably sucking up all available Python developer > round tuits. > > Today I added lockfile usage into Dave Abrahams' safe_pickle function, > in the process renaming it to safe_pickle_write and adding a > corresponding safe_pickle_read. I then replaced all pickle.{dump,load} > calls with the relevant safe_pickle_{write,read} functions. > > This code has not been checked in yet. I've attached a diff against > the current rev 3168. I'm interested in how people think I should > proceed. > Some possibilities: > > * throw it out - we don't need dependencies on external crap > * keep it but pull lockfile into the spambayes package for ease of > distribution > * check the changes in on head > * create a branch and check the changes in there > * get 1.1 out the door, damn it! leave this for 1.2 (around 2011) > * keep the safe_pickle_{read,write} functions but take out the > lockfile > stuff. IMO, the cost of not having locks is greater than the cost of managing such a module. I've no real opinion on how to best manage the code itself, but I'm personally willing to jump through a few small hoops (eg, downloading an external package) to help make this work. On the other hand, expecting *all* users running from source-code (ie, most of the non-Windows world) to download extra packages is error prone - so I'd be happy with CVS users needing to install an external module, but for the source distribution to include it (assuming that isn't too much of a PITA) Cheers, Mark From mhammond at skippinet.com.au Thu Nov 8 01:21:58 2007 From: mhammond at skippinet.com.au (Mark Hammond) Date: Thu, 8 Nov 2007 11:21:58 +1100 Subject: [spambayes-dev] Update PyPI entry for SpamBayes? In-Reply-To: <18225.11703.67003.488335@montanaro.dyndns.org> References: <18225.11703.67003.488335@montanaro.dyndns.org> Message-ID: <03dd01c8219d$732e10c0$598a3240$@com.au> > It seems that the SpamBayes entry in PyPI is a bit outdated. It still > lists > 1.1a2: > > http://pypi.python.org/pypi/spambayes/ > > Anyone got a few minutes to either update the entry or add me as an > owner? > Currently Anthony, Tony, Mark and Richie are listed. It appears Skip is now on that list. Mark From richie at entrian.com Thu Nov 8 23:28:26 2007 From: richie at entrian.com (Richie Hindle) Date: Thu, 08 Nov 2007 22:28:26 +0000 Subject: [spambayes-dev] Update PyPI entry for SpamBayes? In-Reply-To: <03dd01c8219d$732e10c0$598a3240$@com.au> References: <18225.11703.67003.488335@montanaro.dyndns.org> <03dd01c8219d$732e10c0$598a3240$@com.au> Message-ID: <1637j3hjcgtoe9emnlk8cu59tl06vjdjja@4ax.com> [Skip] > http://pypi.python.org/pypi/spambayes/ > Anyone got a few minutes to [...] add me as an owner? [Mark] > It appears Skip is now on that list. That was me - I emailed Skip off-list to say I'd done it (and to apologise for my continuing absence from SpamBayes). Skip, did you see my email? There have been a couple of occasions when I've emailed you privately and had no response - has your SpamBayes installation turned against me? 8-) -- Richie Hindle richie at entrian.com From skip at pobox.com Fri Nov 9 03:51:06 2007 From: skip at pobox.com (skip at pobox.com) Date: Thu, 8 Nov 2007 20:51:06 -0600 Subject: [spambayes-dev] Update PyPI entry for SpamBayes? In-Reply-To: <1637j3hjcgtoe9emnlk8cu59tl06vjdjja@4ax.com> References: <18225.11703.67003.488335@montanaro.dyndns.org> <03dd01c8219d$732e10c0$598a3240$@com.au> <1637j3hjcgtoe9emnlk8cu59tl06vjdjja@4ax.com> Message-ID: <18227.51994.553165.84496@montanaro.dyndns.org> Richie> [Mark] >> It appears Skip is now on that list. Richie> That was me - I emailed Skip off-list to say I'd done it (and to Richie> apologise for my continuing absence from SpamBayes). Richie> Skip, did you see my email? There have been a couple of Richie> occasions when I've emailed you privately and had no response - Richie> has your SpamBayes installation turned against me? 8-) Yup, I got Richie's email. I got all set to get 1.1a4 ready to upload, then realized I'd never created a branch/tag when building 1.1a4. I decided to just wait a little longer for 1.1a5 or 1.1b1, whatever is next. Skip From 735095 at bk.ru Mon Nov 12 17:59:46 2007 From: 735095 at bk.ru (Бетонные блоки 200х200х400) Date: Mon, 12 Nov 2007 19:59:46 +0300 Subject: [spambayes-dev] (no subject) In-Reply-To: <20071112114629.7B508DFA3E3@regionspb.ru> References: <20071112114629.7B508DFA3E3@regionspb.ru> Message-ID: ?????? ????????? ??? ???????? ????? 200?200?400 ?????? ?????????? ??? 89134651001 ?/? (383) 3383544 ------------------------------------ Mail.Ru - ??????, ????????, ???????! ------------------------------------ From oyinjemi at gmail.com Mon Nov 12 19:25:28 2007 From: oyinjemi at gmail.com (Himage Holdings) Date: Mon, 12 Nov 2007 13:25:28 -0500 Subject: [spambayes-dev] Part-time Manager Needed Message-ID: <200711121825.lACIPSY2030887@host24.the-web-host.com> Attention: Would you like to work online from home and get paid weekly? HimageHolding Ltd, Kowloon, Hong Kong. Needs a book keeper, so we want to know if you will like to work onlinefrom home and get paid weekly without leaving or affecting yourpresent job? Himage Holding Ltd., Kowloon, Hong Kong is an electronics firm here in Kowloon, Hong Kong and we need someone to work for the company as a representative/book keeper in the UK,United States, Canada and the rest of Europe countries. Our company produces and deals in all kinds of electronics here in Kowloon, Hong Kong which we have clients we supply weekly all around the globe in the UK, United states, Canada and rest of Europe countries, our clients make payments for our supplies every week via Bank Transfer or Wire Transfer. So we need someone in the UK, United States, and Canada and Europe countries to work as our representative and assist us in processing the payments from our clients and will be entitled to remuneration. All you need to do is to receive payments from our customers in the UK,United States, Canada and Europe countries, deduct 10% commission and send the balance to us. Do let us know if this is of any interest to you by responding via this email address for correspondence (alfred at himagesholding.com). Regards, Mr. Mr Alfred Wagoner. For: Himage Holding Ltd. http://www.himage.com From collardwe1 at cox.net Wed Nov 21 16:15:25 2007 From: collardwe1 at cox.net (William Collard) Date: Wed, 21 Nov 2007 10:15:25 -0500 Subject: [spambayes-dev] Spambayes Buttons not Active Message-ID: <000001c82c51$57c4fd80$0d02a8c0@BILLLAPTOP> When I restarted my Outlook application I got an error message that said Spambayes had a problem and was shutdown. Now the Spambayes buttons show but are not active. How do I reactivate? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/spambayes-dev/attachments/20071121/de4b8af3/attachment.htm