pyzor-users — general discussion of Pyzor and Pyzor-related topics

Re: pyzor reporting failing since change to new server

[Tony M. <to...@sp...>]

> Since the move to the new pyzor server (at least, these errors started
> happening on the 28th April) my script to pick mail from the Spam IMAP
> folder and report & delete has began to report errors.

Thanks Mark, Dave & Bobby, and many apologies for the inconvenience.

I've updated the test script to test "report" as well, and fixed the
error.  It works fine for me now, but please let me know if you have
any more issues and I'll fix them ASAP (although I'm in UTC+1200, so
there may be some delay).

Thanks,
Tony

RE: pyzor reporting failing since change to new server

[Rose, B. <br...@me...>]

Centos 5.2 here and get the same message
public.pyzor.org:24441    (500, "Internal Server Error: global name 'sys' is not defined")


-----Original Message-----
From: Dave Walker [mailto:Dav...@ub...]
Sent: Thursday, April 30, 2009 10:40 AM
To: pyz...@li...
Subject: Re: pyzor reporting failing since change to new server

<SNIP>
> Since the move to the new pyzor server (at least, these errors started
> happening on the 28th April) my script to pick mail from the Spam IMAP
> folder and report & delete has began to report errors.
>
> I'm using Ubuntu 8.04 with the packaged pyzor and the config is set to
> public.pyzor.org.
>
<SNIP>
>
> Thanks,
>
> --
> Mark Fisher

Hi,

Apologies for sending out of thread, I wasn't on the mailing list when
this message appeared.  Just wanted to confirm that I am experiencing
the same situation.

$ public.pyzor.org has address 89.18.189.160
89.18.189.160

$ pyzor --homedir /etc/mail/spamassassin ping
public.pyzor.org:24441    (200, 'OK')

$ pyzor --homedir /etc/mail/spamassassin report <  $somemail
public.pyzor.org:24441    (500, "Internal Server Error: global name
'sys' is not defined")

Ubuntu Hardy 8.04.2

Kind Regards,
Dave Walker

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations
Conference from O'Reilly Media. Velocity features a full day of
expert-led, hands-on workshops and two days of sessions from industry
leaders in dedicated Performance & Operations tracks. Use code vel09scf
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
pyzor-users mailing list
pyz...@li...
https://lists.sourceforge.net/lists/listinfo/pyzor-users

This document may include proprietary and confidential information of Wayne State University Physician Group and may only be read by those person(s) to whom it is addressed. If you have received this e-mail message in error, please notify us immediately. This document may not be reproduced, copied, distributed, published, modified or furnished to third parties, without prior written consent of Wayne State University Physician Group. Thank you.

Re: pyzor reporting failing since change to new server

[Dave W. <Dav...@ub...>]

<SNIP>
> Since the move to the new pyzor server (at least, these errors started
> happening on the 28th April) my script to pick mail from the Spam IMAP
> folder and report & delete has began to report errors.
>
> I'm using Ubuntu 8.04 with the packaged pyzor and the config is set to
> public.pyzor.org.
>
<SNIP>
>
> Thanks,
>
> --
> Mark Fisher

Hi,

Apologies for sending out of thread, I wasn't on the mailing list when
this message appeared.  Just wanted to confirm that I am experiencing
the same situation.

$ public.pyzor.org has address 89.18.189.160
89.18.189.160

$ pyzor --homedir /etc/mail/spamassassin ping
public.pyzor.org:24441    (200, 'OK')

$ pyzor --homedir /etc/mail/spamassassin report <  $somemail
public.pyzor.org:24441    (500, "Internal Server Error: global name
'sys' is not defined")

Ubuntu Hardy 8.04.2

Kind Regards,
Dave Walker

pyzor reporting failing since change to new server

[Mark F. <mar...@na...>]

Hi,

Since the move to the new pyzor server (at least, these errors started
happening on the 28th April) my script to pick mail from the Spam IMAP
folder and report & delete has began to report errors.

I'm using Ubuntu 8.04 with the packaged pyzor and the config is set to
public.pyzor.org.

I can see a connection going to 89.18.189.160 on UDP 24441, but turning
on debug shows an internal server error.  Pasted below.

pyzor[9223]:
sending: 'User: anonymous\nTime: 1241089270\nSig:
0e1d8ab5b201475af9ae61bf7733c514c2a0fd5f\n\nOp: report\nOp-Digest:
62782786137a0bca2ec7b5cf3d922293da72e65b\nOp-Spec: 20,3,60,3\nThread:
6919\nPV: 2.0\n\n'
received: "Code: 500\nDiag: Internal Server Error: global name 'sys' is
not defined\nThread: 6919\nPV: 2.0\n\n"

Thanks,

--
  Mark Fisher

RE: Pyzor 0.5.0 release candidate

[Benedict W. <Ben...@cs...>]

-----Original Message-----
From: Tony Meyer [mailto:to...@sp...]
Sent: 29 April 2009 22:03
To: pyz...@li...
Subject: Pyzor 0.5.0 release candidate

Hi,

I believe pyzor 0.5 is all ready to go.  This is a bugfix release,
mostly patches contributed from the Debian pyzor package.  The purpose
of the release is basically to clear up old issues, so that we can
continue to bring pyzor back to a more active project.

>>

Many thanks for the hard work!


Kind Regards

Benedict White

Tel: 01444 238070 Tech: 01444 238080 Fax: 01444 238099 Web: http://www.cse-ltd.co.uk   Registered in England and Wales No: 3066242
27 Victoria Gardens, Burgess Hill, West Sussex, RH15 9NB

RE: Supported versions of Python

[Benedict W. <Ben...@cs...>]

-----Original Message-----
From: Tony Meyer [mailto:to...@sp...]
Sent: 29 April 2009 21:50
To: pyz...@li...
Subject: Re: Supported versions of Python

> I meant who is working on a new version of Pyzor?

At the moment, I am, and I believe that's basically it.  More help is
(of course) always welcome.

I have a new release basically ready to go - it's just bug fixes (the
majority contributed back from the Debian pyzor package, so well
tested).  I attempted to resolve all the outstanding bug reports and
patch submissions - work on feature requests can start after this one
goes out.  I believe all the changes are on the client side.
>>

Well done, have you got the patches for the server side from Frank Tobin?

If not I will have a look for them.

Kind regards



Kind Regards

Benedict White

Tel: 01444 238070 Tech: 01444 238080 Fax: 01444 238099 Web: http://www.cse-ltd.co.uk   Registered in England and Wales No: 3066242
27 Victoria Gardens, Burgess Hill, West Sussex, RH15 9NB

New public Pyzor server

[Dreas v. D. <dr...@sp...>]

Hi,

Yesterday we have changed the public Pyzor server to a new machine on a 
new IP. The server has had some significant upgrades, and should better 
cope with the volume of requests.

Everybody that is already querying the hostname public.pyzor.org will 
not have to take any actions. If you are not using the public.pyzor.org 
hostname yet, please run "pyzor discover" to correctly set your pyzor 
client. To see what server you are currently using, you can simply run 
"pyzor ping".

If you experience any problems (e.g. timeouts, or the requests are still 
too slow) please do let us know via the 
pyz...@li... mailinglist.

Kind regards,

Dreas

Pyzor 0.5.0 release candidate

[Tony M. <to...@sp...>]

Hi,

I believe pyzor 0.5 is all ready to go.  This is a bugfix release,
mostly patches contributed from the Debian pyzor package.  The purpose
of the release is basically to clear up old issues, so that we can
continue to bring pyzor back to a more active project.

In theory, this should be quite stable, since it's only bugfixes, and
most of those have been actively used by Debian users for some time.
However, it's also the first pyzor release that I've done, and the
first release for many years, so it's quite possible that there could
be subtle issues (e.g. with packaging), too.

If anyone has time to try out the release candidate code over the next
week, that would be greatly appreciated.  The official release will
appear on the normal sourceforge download page, but in the meantime
you can get a release candidate from:

http://download.spamexperts.com/pyzor-0.5.0rc1.tar.gz
http://download.spamexperts.com/pyzor-0.5.0rc1.tar.bz2

Thanks,
Tony

Re: Supported versions of Python

[Benny P. <me...@ju...>]

On Wed, April 29, 2009 22:50, Tony Meyer wrote:
>> I meant who is working on a new version of Pyzor?
>
> At the moment, I am, and I believe that's basically it.  More help is
> (of course) always welcome.

http://bugs.gentoo.org/216374

was my work on gentoo, still in use here, would be happy to help if i can

-- 
http://localhost/ 100% uptime and 100% mirrored :)

Re: Supported versions of Python

[Tony M. <to...@sp...>]

> I meant who is working on a new version of Pyzor?

At the moment, I am, and I believe that's basically it.  More help is
(of course) always welcome.

I have a new release basically ready to go - it's just bug fixes (the
majority contributed back from the Debian pyzor package, so well
tested).  I attempted to resolve all the outstanding bug reports and
patch submissions - work on feature requests can start after this one
goes out.  I believe all the changes are on the client side.

In addition, I've also been working on the server code.  The existing
code was struggling to keep up with requests, even with modern
hardware.  I've modified the server code so that it's reasonably easy
to add support for different database backends - the existing gdbm
database should still work, and I've got an example MySQL
implementation (postgreSQL, sqlite, ZODB, etc, should be simple to
add, if anyone had use for that).

I think an announcement post may come soon covering this, but as of a
couple of days ago, this new server code is live.  However, it's not
yet checked into SVN - I'd like this upcoming release to be totally
bugfixes, so will check in the changes as soon as I manage to get the
release done.  I'm pretty sure that nearly all pyzor users are only
interested in the client code (and using the public server), so there
doesn't seem to be too much of a hurry.

> Is there any testing I can help with,
> or I could possibly run a test peering server in our offices if that helps.

Thanks.  I think as far as the server goes, it's easy enough for me to
test here (on a dev server first, and then live).  Testing the client
would certainly be useful, particularly as we start moving into adding
new features.  Feel free to comment on any of the feature tickets (on
sourceforge: https://sourceforge.net/tracker/?group_id=50000&atid=458245),
too, if you want to weigh in on what you think would be worth
adding/changing.

Cheers,
Tony

Re: sitewide config for pyzor

[Tony M. <to...@sp...>]

> It seems that pyzor does not support site-wide config file. Is there
> apossibility to add this?

Yes.  The best thing to do would be to open a feature request ticket
at https://sourceforge.net/tracker/?group_id=50000&atid=458245

> I think that having site-wide config at least for definong servers would be
> a good idea.

I think servers and timeout would be reasonable to have as server-wide
configuration options.

Cheers,
Tony

Re: pyzor automatic submission

[Tony M. <to...@sp...>]

> Some time ago I have noticed that mails like monthly mailing list reports
> are listed in pyzor. I strongly doubt that such mails are feed to pyzor
> manually and I guess someone has implemented automatic submission for
> detected spam.
>
> Is this correct? Razor docs say that only manual submissions should be done
> and I'd expect the same from pyzor, however I haven't found any reference...

At the moment, there's no restriction over who can submit, so there's
effectively no way of controlling what is submitted - we have to trust
that people are only submitting true spam.  It's quite possible that
there are people that are automatically submitting, but there isn't
much that can be done about that, as far as I can see.  It's also
possible that people are submitting these as spam manually - end-users
have a bad habit of submitting as spam things that they legitimately
signed up for, but no longer have interest in, and are too lazy to
unsubscribe from.  There's not much that can be done about that,
either, unfortunately.

My best suggestion is that I would guess that messages like this have
a reasonably low hit count (e.g. instead of a hundred reports, there
are fewer than 10).  By adjusting the threshold that you use for a
Pyzor result to be considered spam, you might be able to avoid
triggering on these messages.

Cheers,
Tony

RE: Supported versions of Python

[Benedict W. <Ben...@cs...>]

Just to be clear, when I said:
"On another note, who is working on open source development?"

I meant who is working on a new version of Pyzor? Is there any testing I can help with,
or I could possibly run a test peering server in our offices if that helps.

(I am also pleased Pyzor is staying open source)

Kind Regards

Benedict White


Tel:
01444 238070
Tech:
01444 238080
Fax:
01444 238099
Web:
http://www.cse-ltd.co.uk


Registered in England and Wales No: 3066242
27 Victoria Gardens, Burgess Hill, West Sussex, RH15 9NB

Re: Supported versions of Python

[Benedict W. <Ben...@cs...>]

On the distribution of Linux I use, (arch Linux) we are still on Python 2.6x, so as long as that is supported I don't mind.

On another note, who is working on open source development?

Kind Regards

Benedict White


Tel:
01444 238070
Tech:
01444 238080
Fax:
01444 238099
Web:
http://www.cse-ltd.co.uk


Registered in England and Wales No: 3066242
27 Victoria Gardens, Burgess Hill, West Sussex, RH15 9NB

sitewide config for pyzor

[Matus U. - f. <uh...@fa...>]

Hello,

It seems that pyzor does not support site-wide config file. Is there
apossibility to add this?

I think that having site-wide config at least for definong servers would be
a good idea. For now I configures SpamAssassin to call pyzor with --homedir
option, but this disallows usage of per-user directories
-- 
Matus UHLAR - fantomas, uh...@fa... ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
He who laughs last thinks slowest. 

pyzor automatic submission

[Matus U. - f. <uh...@fa...>]

Hello,

Some time ago I have noticed that mails like monthly mailing list reports
are listed in pyzor. I strongly doubt that such mails are feed to pyzor
manually and I guess someone has implemented automatic submission for
detected spam.

Is this correct? Razor docs say that only manual submissions should be done
and I'd expect the same from pyzor, however I haven't found any reference...

-- 
Matus UHLAR - fantomas, uh...@fa... ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Honk if you love peace and quiet. 

Re: Supported versions of Python

[Javier Sánchez-A. D. <jav...@co...>]

Robert Terzi wrote:
> Andreas Schamanek wrote:
>   
>> On Tue, 7 Apr 2009, at 11:28, Tony Meyer wrote:
>>
>>     
>>> ... what would be your preference for continued development?
>>>       
>> My servers (and those I care most about) run Debian. Debian currently 
>> has Python 3.1 already/at least in the Experimental branch, see 
>> http://packages.debian.org/python3 . Hence, I vote for migration to 
>> Python 3+.
>>     
>
> My vote is for the opposite.  I expect many mail servers that run
> pyzor will be production machines, not necessarily running the
> latest python or linux distribution.
>
> It's probably worth looking into what the plans are for GNU Mailman
> (w.r.t. supported python versions) as it is reasonably likely that both
> packages would be desired on mail servers.  Requiring Python 3
> for a current version of Pyzor in advance of critical mass for
> python 3 could be an unnecessary burden on admins.  The result
> could possibly be less sites running pyzor.
>   

I agree with Robert too. Still the most part of production servers are 
running v2.x . If pyzor change to version 3 "so soon" I think there will 
be many admins that will stop to use it.

My vote is for continue using version 2.x

HTH,
-- 

 

*Javier Sánchez-Arévalo Díaz*
Dpto. de Informática del COAM 	

	Tfno: 91 595 15 36
*web*: www.coam.es 	c\ Barquillo Nº 12,  5ª Planta

*mail*: jav...@co... <mailto:jav...@co...>

	

28004 Madrid

Este correo electrónico y, en su caso, cualquier fichero anexo al mismo, 
contiene información de carácter confidencial exclusivamente dirigida a 
su destinatario o destinatarios. Queda prohibida su divulgación, copia o 
distribución a terceros sin la previa autorización escrita del COLEGIO 
OFICIAL DE ARQUITECTOS DE MADRID.
En el caso de haber recibido este correo electrónico por error, se ruega 
notifíquese inmediatamente esta circunstancia mediante reenvío a la 
dirección electrónica del remitente o al teléfono 91 595 15 28
De conformidad con lo establecido en la L.O.P.D. 15/1999, el COLEGIO 
OFICIAL DE ARQUITECTOS DE MADRID garantiza la adopción de las medidas 
necesarias para asegurar el tratamiento confidencial de los datos de 
carácter personal. Así mismo le informamos de la posibilidad de ejercer 
los derechos de acceso, rectificación, cancelación y oposición en la 
siguiente dirección: c/Barquillo 12. Madrid 28004


<http://www.coam.es/>

Re: Supported versions of Python

[Edward B. <ed...@ba...>]

Hi there,

Tony Meyer wrote:

>  * Continue with the 2.x line (the last time I checked, there is at
> least 2.7 scheduled, and there could be a 2.8 or even 2.9), including
> support for older versions of 2.x.

Python 2.x is still the latest version of Python on 99% of machines 
running Python.  Until distros catch up, I think it makes sense to view 
Python 3.x as the future, e.g. not the present.  There's little risk in 
continuing with Python 2.x as development platform for the next 3 years 
(probably longer).  Since Python 3.x is intentionally not backwards 
compatible, adoption will be slow.

>  * Create a 3.x branch, and have separate releases for 2.x and 3.x
> (note that this is obviously the most work, since there are two
> diverging sets of code to maintain and develop, so there would have to
> be a real need for this).

Ideally, one set of code supports BOTH 2.x and 3.x.  You could add a 
configuration variable that asks for Python version and where there are 
code differences between the two, run different code blocks.  I admit it 
could get very messy doing this but users would be happy.  When 2.x 
becomes legacy, you can just remove these conditional blocks.

>  * Start discontinuing support for old versions of Python after the
> next Pyzor release (coming very soon).  I suspect that 2.5 could be
> maintained while supporting a 3.x version (using the 2to3 tool),
> although it's possible that 2.6 would have to be the minimum required.
>  This wouldn't be a "rewrite", just tidying up older code (e.g. the
> style of raising exceptions).
> 
> Obviously, old versions of Pyzor continue to work with old versions of
> Python, no matter what.  The upcoming Pyzor release should work with
> any 2.x version of Python.

Eventually, Python 3.x support will be great and much desired.  But I 
don't think the demand is there yet.  Users just want a working Pyzor 
that does what Pyzor claims to do.  If Python 3.x development today 
comes at the expense of a stable 2.x version, then I say bad idea.  But 
if both 2.x and 3.x can be supported equally well, then go for it.

Ed

> 
> Thanks,
> Tony

Re: Supported versions of Python

[Andreas S. <sch...@fa...>]

> On Tue, 2009-04-07 at 10:30 -0400, Robert Terzi wrote:
>> Andreas Schamanek wrote:
>>> On Tue, 7 Apr 2009, at 11:28, Tony Meyer wrote:
>>>> ... what would be your preference for continued development?
>>> ... Debian currently has Python 3.1 already/at least in the 
>>> Experimental branch, see http://packages.debian.org/python3 . 
>>> Hence, I vote for migration to Python 3+.
>> 
>> My vote is for the opposite.  I expect many mail servers that run 
>> pyzor will be production machines, not necessarily running the 
>> latest python or linux distribution.

I am with you. My vote is based on the wild guess that Python 3 will 
be part of the next stable Debian release ("Squeeze"), and on the fact 
that running multiple versions of Python on the same system is rather 
easy, in fact it is supported in Debian.

HTH,

-- 
-- Andreas

Re: Supported versions of Python

[John H. <joh...@pl...>]

On Tue, 2009-04-07 at 10:30 -0400, Robert Terzi wrote:
> Andreas Schamanek wrote:
> > On Tue, 7 Apr 2009, at 11:28, Tony Meyer wrote:
> > 
> >> ... what would be your preference for continued development?
> > 
> > My servers (and those I care most about) run Debian. Debian currently 
> > has Python 3.1 already/at least in the Experimental branch, see 
> > http://packages.debian.org/python3 . Hence, I vote for migration to 
> > Python 3+.
> 
> My vote is for the opposite.  I expect many mail servers that run
> pyzor will be production machines, not necessarily running the
> latest python or linux distribution.
> 
CentOS 5.3 servers here, using Python 2.4.3.
Fedora 11 (development) seems to currently have Python 2.6.


John.

-- 
---------------------------------------------------------------
John Horne, University of Plymouth, UK  Tel: +44 (0)1752 587287
E-mail: Joh...@pl...       Fax: +44 (0)1752 587001

Re: Supported versions of Python

[Robert T. <rc...@r-...>]

Andreas Schamanek wrote:
> On Tue, 7 Apr 2009, at 11:28, Tony Meyer wrote:
> 
>> ... what would be your preference for continued development?
> 
> My servers (and those I care most about) run Debian. Debian currently 
> has Python 3.1 already/at least in the Experimental branch, see 
> http://packages.debian.org/python3 . Hence, I vote for migration to 
> Python 3+.

My vote is for the opposite.  I expect many mail servers that run
pyzor will be production machines, not necessarily running the
latest python or linux distribution.

It's probably worth looking into what the plans are for GNU Mailman
(w.r.t. supported python versions) as it is reasonably likely that both
packages would be desired on mail servers.  Requiring Python 3
for a current version of Pyzor in advance of critical mass for
python 3 could be an unnecessary burden on admins.  The result
could possibly be less sites running pyzor.

HTH,
--Rob

Re: Supported versions of Python

[Andreas S. <sch...@fa...>]

On Tue, 7 Apr 2009, at 11:28, Tony Meyer wrote:

> ... what would be your preference for continued development?

My servers (and those I care most about) run Debian. Debian currently 
has Python 3.1 already/at least in the Experimental branch, see 
http://packages.debian.org/python3 . Hence, I vote for migration to 
Python 3+.

HTH,

-- 
-- Andreas

Supported versions of Python

[Tony M. <to...@sp...>]

I've responded to Mark in the tracker (
https://sourceforge.net/support/tracker.php?aid=2738312 ), but I'm
interested in knowing how much demand for this there is.

Basically, the situation is that Python 3.x is not (completely)
backwards compatible with Python 2.x.  It depends on the code (and I
haven't looked at pyzor specifically in this regard yet), but it is
reasonably likely that a single set of code cannot support both Python
2.5 (and earlier) and Python 3.x.  The hope is that code can be
written to support both Python 2.6 and Python 3.x (using various
future imports in the 2.6 version).

Some changes can be handled automatically (with manual verification)
by the Python 2to3 tool.  Other changes require code to be manually
re-written.

At the moment, pyzor works with very old versions of Python (at least
2.2, possibly even earlier).  Supporting versions that old as well as
3.x is basically unfeasible (i.e. there needs to be two branches of
the code, one for 2.x, and one for 3.x, although the 3.x one might be
usable in Python 2.6+).

For those that are still around on this list (and please forward this
query on to any other interested parties), what would be your
preference for continued development?

 * Continue with the 2.x line (the last time I checked, there is at
least 2.7 scheduled, and there could be a 2.8 or even 2.9), including
support for older versions of 2.x.

 * Create a 3.x branch, and have separate releases for 2.x and 3.x
(note that this is obviously the most work, since there are two
diverging sets of code to maintain and develop, so there would have to
be a real need for this).

 * Start discontinuing support for old versions of Python after the
next Pyzor release (coming very soon).  I suspect that 2.5 could be
maintained while supporting a 3.x version (using the 2to3 tool),
although it's possible that 2.6 would have to be the minimum required.
 This wouldn't be a "rewrite", just tidying up older code (e.g. the
style of raising exceptions).

Obviously, old versions of Pyzor continue to work with old versions of
Python, no matter what.  The upcoming Pyzor release should work with
any 2.x version of Python.

Thanks,
Tony

Re: SyntaxError after upgrade to Python 3.0

[Eduardo C. <edu...@in...>]

i think that pyzor code is for python 2.6.1 and not for 3.0. But like all apps writen in 2.6.x they cannot be switched to 3.0 directly, they need to be ported. 

my opinion is that you should use python 2.6.1 


----- "Mark" <ad...@as...> wrote: 
> 
> 

Hello, 



Getting a little frustrated. Trying to install pyzor again, after 

upgrading to Python 3.0, and I keep getting: 





{root} % /usr/local/bin/pyzor check < /temp/gtube.txt 

Traceback (most recent call last): 

File "/usr/local/bin/pyzor", line 3, in <module> 

import pyzor.client 

File "/usr/local/lib/python3.0/site-packages/pyzor/__init__.py", line 84 

raise ValueError, "%s is an invalid username" % self 

^ 

SyntaxError: invalid syntax 





Does anyone know what's going on? 



Thanks, 



- Mark 
> ------------------------------------------------------------------------------ 
> _______________________________________________ pyzor-users mailing list pyz...@li... https://lists.sourceforge.net/lists/listinfo/pyzor-users 

-- 
----- 
Eduardo Casarero 
Informatica Avanzada SRL 
Email: edu...@in... 
Tel: (054) 011-52353939 int 115 

SyntaxError after upgrade to Python 3.0

[Mark <ad...@as...>]

Hello,

 

Getting a little frustrated. Trying to install pyzor again, after

upgrading to Python 3.0, and I keep getting:

 

 

{root} % /usr/local/bin/pyzor check < /temp/gtube.txt

Traceback (most recent call last):

  File "/usr/local/bin/pyzor", line 3, in <module>

    import pyzor.client

  File "/usr/local/lib/python3.0/site-packages/pyzor/__init__.py", line 84

    raise ValueError, "%s is an invalid username" % self

                    ^

SyntaxError: invalid syntax

 

 

Does anyone know what's going on?

 

Thanks,

 

- Mark