xmpppy-devel — Main place to discuss problems request features and to get support.

[Xmpppy-devel] Re: status?

[Alexey N. <sn...@pe...>]

=F7 =D3=CF=CF=C2=DD=C5=CE=C9=C9 =CF=D4 11 =ED=C1=CA 2004 10:57 Cosimo Alfar=
ano =CE=C1=D0=C9=D3=C1=CC(a):
> On Tue, May 11, 2004 at 08:16:12AM +0400, Alexey Nezhdanov wrote:
> > packaging errors you will send me a notice about it and let me make such
> > changes myself.
> > In the same time I have thought that .orig.tar.gz file is always matches
> > original file that was uploaded to the product's download page. And that
> > the .diff.gz file reflects the changes that Debian developer made to
> > _tarball_ - not the source code only.
> > And the any person can compare md5's of both tarballs and be sure that
> > they matches.
> > So since you have changed original tarball - there is no point to
> > keep .orig.tar.gz and .diff.gz files as separate ones - there is no any
> > original files anymore only modifyed ones IMHO.
>
> Actually orig is not the original upstream's tarball everytime, some
> packages has orig containing the tarball (ie no md5 issues)
>
> Anyway, this is a minor point. When it will uploaded, we can modify it
> every time we need.
>
> > In the ideal I'd like to make the debian uploads with two core
> > files: .orig.tar.gz and .dsc - i.e. without .diff.gz file.
> > If such behaivoir is violation of Debian uploads policy please inform m=
e.
>
> packages without targz are "debian native", ie packages written by
> debian for debian. I'd prefer to have a diff file.
>
> It's OK to have all the stuff in CVS, but a difffile should be present.
>
> 	c.
Ok. So we can now relax a little and continue our work.

=2D-=20
Respectfully
Alexey Nezhdanov

Re: [Xmpppy-devel] what to read?

[Alexey N. <sn...@pe...>]

=F7 =D3=CF=CF=C2=DD=C5=CE=C9=C9 =CF=D4 5 =ED=C1=CA 2004 12:20 gabor =CE=C1=
=D0=C9=D3=C1=CC(a):
> hi,
>
> i have been thinking about writing a very very very simple jabber client
> in python...nothing serious, just for fun...
>
> question:
>
> what documents should i read about jabber?
>
> i know there are 2 documents in the xmpppy distribution, but isn't there
> a less formal one?
xmpppy distribution includes one document: README.py. It is a simple script=
=20
that can connect to a server and nothing more.

CVS version contains also copies of xmpp-core and xmpp-im documents (probab=
ly=20
the "formal ones" that you are speaking about).

there are no good documentation about xmpppy usage AFAIK. I'm planning to=20
write it for 0.2 release.

In the meantime you can try reading some jabberpy-based scripts or even=20
xmpppy-based (CVS's irc-transport for example).

Also you can look into very simple rss-transport in the attachment (especia=
lly=20
at the lines 50,51,52,59,34 :)) ).

=2D-=20
Respectfully
Alexey Nezhdanov

Re: [Xmpppy-devel] what to read?

[Ian Stokes-R. <i.s...@ph...>]

It already exists, I would say.  The jabberpy distribution has a 
"test_client" which is a very very very simple jabber client, written in 
python.  Knock yourself out if you want to write another one.

What to read?  Probably looking at the jabberpy code is as good a start 
as any.

Ian

gabor wrote:
> hi,
> 
> i have been thinking about writing a very very very simple jabber client
> in python...nothing serious, just for fun...
> 
> question:
> 
> what documents should i read about jabber?
> 
> i know there are 2 documents in the xmpppy distribution, but isn't there
> a less formal one?

-- 
Ian Stokes-Rees                 i.s...@ph...
Particle Physics, Oxford        http://www-pnp.physics.ox.ac.uk/~stokes

[Xmpppy-devel] what to read?

[gabor <ga...@z1...>]

hi,

i have been thinking about writing a very very very simple jabber client
in python...nothing serious, just for fun...

question:

what documents should i read about jabber?

i know there are 2 documents in the xmpppy distribution, but isn't there
a less formal one?

gabor

Re: [Xmpppy-devel] Register new user to jabber server

[Alexey N. <sn...@pe...>]

=D0=92 =D1=81=D0=BE=D0=BE=D0=B1=D1=89=D0=B5=D0=BD=D0=B8=D0=B8 =D0=BE=D1=82 =
30 =D0=90=D0=BF=D1=80=D0=B5=D0=BB=D1=8C 2004 11:53 Frank Matthie=C3=9F =D0=
=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB(a):
> Alexey Nezhdanov [2004-04-29 20:58 CEST]:
> > Frank Matthie=C3=9F wrote:
> > >Hello,
> > >
> > >i like to play with python(2.3) and jabber(1.4) and have at least one
> > >question.
> > >
> > >How do i register a new user to the jabber server. A look inside the
> > >modules doesn't help me.
> > >
> > >Version: python2.3-xmpp 0.1-pre4-1 (debian testing)
> > >        jabber         1.4.2a-12  (debian testing)
> > >        python2.3      2.3.3-6    (debian testing)
> > >
> > >My first approach failed, because i first not very familar with python
> > >and second miss the point that disp is an Dispatcher object.
> > >
> > >Inside client.py line 101 the connect get plug in. But were ist the
> > >Dispacther object reference? This should be a silly question, but this
> > >is not clear for me.
> >
> > Do not understand your question.
> > client.py (lines 100,101):
> >        dispatcher.Dispatcher().PlugIn(self)
> >        while self.Dispatcher.Stream._document_attrs is None:
> > self.Process(1)
> > line 100 plugs the Dispatcher object into client, line 101 uses it.
> > line "self.Dispatcher=3Dsmth" absent since PlugIn method does it.
>
> Thanks for explanation. That's what i mean with "not famliar with
> python". I take my first or second steps in python programming.
This is not the "native" python stuff. PlugIn uses unusual approach for=20
setting client's instance attributes. Do not expect such behaivour in other=
=20
python programs.

> > diff -ur base/features.py cur/features.py
> > --- base/features.py	2004-04-29 22:27:29.000000000 +0400
> > +++ cur/features.py	2004-04-29 21:27:52.000000000 +0400
> > @@ -82,32 +82,41 @@
> >      return identities , features
> >
> >  ### Registration ### jabber:iq:register ### JEP-0077
> > ########################### -def getRegInfo(disp,jid,info=3D{}):
> > -    iq=3DIq('get',NS_REGISTER,to=3Djid)
> > +def getRegInfo(disp,host,info=3D{}):
> > +    """Gets registration blank from host.
> > +       disp must be connected dispatcher instance."""
> > +    iq=3DIq('get',NS_REGISTER,to=3Dhost)
> >      for i in info.keys(): iq.setTagData(i,info[i])
> >      resp=3Ddisp.SendAndWaitForResponse(iq)
> > -    if not isResultNode(rep): return
> > +    if not isResultNode(resp): return
>
> Wrong: This must be "if not resultNode(resp): return". Thast the reason,
> why this patch failed.

:) I think that patch was succeeded but library not worked. Yes you are rig=
ht.
Appears that I have cutted out the needed stuff.
Try 0.1-pre5 - it must work properly.

=2D-=20
Respectfully
Alexey Nezhdanov

Re: [Xmpppy-devel] Register new user to jabber server

[Frank <fr...@lu...>]

Alexey Nezhdanov [2004-04-29 20:58 CEST]:
> Frank Matthie=DF wrote:
>=20
> >Hello,
> >
> >i like to play with python(2.3) and jabber(1.4) and have at least one
> >question.
> >
> >How do i register a new user to the jabber server. A look inside the
> >modules doesn't help me.=20
> >
> >Version: python2.3-xmpp 0.1-pre4-1 (debian testing)
> >        jabber         1.4.2a-12  (debian testing)
> >        python2.3      2.3.3-6    (debian testing)
> >
> >My first approach failed, because i first not very familar with python
> >and second miss the point that disp is an Dispatcher object.
> >
> >Inside client.py line 101 the connect get plug in. But were ist the
> >Dispacther object reference? This should be a silly question, but this
> >is not clear for me.
> >
> Do not understand your question.
> client.py (lines 100,101):
>        dispatcher.Dispatcher().PlugIn(self)
>        while self.Dispatcher.Stream._document_attrs is None:=20
> self.Process(1)
> line 100 plugs the Dispatcher object into client, line 101 uses it.
> line "self.Dispatcher=3Dsmth" absent since PlugIn method does it.

Thanks for explanation. That's what i mean with "not famliar with
python". I take my first or second steps in python programming.=20

>=20
> >
> >How to register a new user to the jabber server?
> >
> Hmmm. It seems that registering new user is broken in pre4. Fix=20
> (attached) is now incorporated in CVS.
> Example of use:
>=20
> cl=3Dclient.Client('home1.penza-gsm.ru')
> cl.connect()
> blank=3DgetRegInfo(cl,'home1.penza-gsm.ru')
> blank['username']=3D'testreg1'
> blank['password']=3D'testregpass1'
> register(cl,'home1.penza-gsm.ru',blank)

This run perfect. Thanks Alexey.

> diff -ur base/features.py cur/features.py
> --- base/features.py	2004-04-29 22:27:29.000000000 +0400
> +++ cur/features.py	2004-04-29 21:27:52.000000000 +0400
> @@ -82,32 +82,41 @@
>      return identities , features
> =20
>  ### Registration ### jabber:iq:register ### JEP-0077 ###################=
########
> -def getRegInfo(disp,jid,info=3D{}):
> -    iq=3DIq('get',NS_REGISTER,to=3Djid)
> +def getRegInfo(disp,host,info=3D{}):
> +    """Gets registration blank from host.
> +       disp must be connected dispatcher instance."""
> +    iq=3DIq('get',NS_REGISTER,to=3Dhost)
>      for i in info.keys(): iq.setTagData(i,info[i])
>      resp=3Ddisp.SendAndWaitForResponse(iq)
> -    if not isResultNode(rep): return
> +    if not isResultNode(resp): return

Wrong: This must be "if not resultNode(resp): return". Thast the reason,
why this patch failed.

Frank.
--=20
Frank Matthie=DF

Terrorists can take my live.
Only the government can take my freedom.

Re: [Xmpppy-devel] Register new user to jabber server

[Alexey N. <sn...@pe...>]

Frank Matthieß wrote:

>Hello,
>
>i like to play with python(2.3) and jabber(1.4) and have at least one
>question.
>
>How do i register a new user to the jabber server. A look inside the
>modules doesn't help me. 
>
>Version: python2.3-xmpp 0.1-pre4-1 (debian testing)
>         jabber         1.4.2a-12  (debian testing)
>         python2.3      2.3.3-6    (debian testing)
>
>My first approach failed, because i first not very familar with python
>and second miss the point that disp is an Dispatcher object.
>
>Inside client.py line 101 the connect get plug in. But were ist the
>Dispacther object reference? This should be a silly question, but this
>is not clear for me.
>
Do not understand your question.
client.py (lines 100,101):
        dispatcher.Dispatcher().PlugIn(self)
        while self.Dispatcher.Stream._document_attrs is None: 
self.Process(1)
line 100 plugs the Dispatcher object into client, line 101 uses it.
line "self.Dispatcher=smth" absent since PlugIn method does it.

>
>How to register a new user to the jabber server?
>
Hmmm. It seems that registering new user is broken in pre4. Fix 
(attached) is now incorporated in CVS.
Example of use:

cl=client.Client('home1.penza-gsm.ru')
cl.connect()
blank=getRegInfo(cl,'home1.penza-gsm.ru')
blank['username']='testreg1'
blank['password']='testregpass1'
register(cl,'home1.penza-gsm.ru',blank)

>Frank.
>

--
Respectfully
Alexey Nezhdanov.

[Xmpppy-devel] Register new user to jabber server

[Frank <fr...@lu...>]

Hello,

i like to play with python(2.3) and jabber(1.4) and have at least one
question.

How do i register a new user to the jabber server. A look inside the
modules doesn't help me.=20

Version: python2.3-xmpp 0.1-pre4-1 (debian testing)
         jabber         1.4.2a-12  (debian testing)
         python2.3      2.3.3-6    (debian testing)

My first approach failed, because i first not very familar with python
and second miss the point that disp is an Dispatcher object.

Inside client.py line 101 the connect get plug in. But were ist the
Dispacther object reference? This should be a silly question, but this
is not clear for me.

How to register a new user to the jabber server?

Frank.
--=20
Frank Matthie=DF

  In the beginning was the word, and the word was content-type: text/plain

[Xmpppy-devel] Upcoming stable release

[Alexey N. <sn...@pe...>]

Hello.

xmpppy's IBB (JEP-0047) realisation hit the debug phase on monday.
Unfortunately I have no time at the moment to kill the bugs but I think that I 
can do it this week.
After this xmpppy will enter rc-series so if you want to see some features in 
stable (0.1) release it is proper time to do so now.

-- 
Respectfully
Alexey Nezhdanov

Re: [Xmpppy-devel] xmpppy, say hello world

[Peter Saint-A. <st...@ja...>]

On Tue, Jan 20, 2004 at 04:40:17AM +0000, Luis Marques wrote:
> On Tuesday 20 January 2004 03:16, Alexey Nezhdanov wrote:
> 
> """3. You may opt to apply the terms of the ordinary GNU General Public 
> License instead of this License to a given copy of the Library. To do this, 
> you must alter all the notices that refer to this License, so that they refer 
> to the ordinary GNU General Public License, version 2, instead of to this 
> License. (If a newer version than version 2 of the ordinary GNU General 
> Public License has appeared, then you can specify that version instead if you 
> wish.) Do not make any other change in these notices. 
> 
> Once this change is made in a given copy, it is irreversible for that copy, so 
> the ordinary GNU General Public License applies to all subsequent copies and 
> derivative works made from that copy."""

Sure, it's basically a fork of (some of) the code  at this point.

> As someone else would say, Jabber on!

Hey, did I give you permission to quote me on that? ;-)

BTW, I think there are a few other Jabber libraries that are GPL,
specifically JOPL (used to power Exodus) and PHPJabberClass.

/psa

Re: [Xmpppy-devel] xmpppy, say hello world

[Luis M. <lui...@ne...>]

On Tuesday 20 January 2004 03:16, Alexey Nezhdanov wrote:

> :)) Never buyed a car. But I know how the new computer smells... It's=20
> amasing.

Indeed. I also like the smell of new leather-like sofas :)

> Try JAJC. It is well designed and well written client with proprietary
> license. It is copied free but non-free since no source code comes with i=
t.

Yes, it's a nice program. But it doesn't run on linux and it's not free. So=
=20
it's not particularly tempting, as there are other programs of the same=20
quality.

> Do not sure. I have not ever read LGPL :) If you will found that this is
> illegal - leave me a note - I will replace all jabberpy code with mine.
> But I am think that it is legal. Free license (LGPL) allows derived
> products to be less free than itself. I will be very surprised if it
> prevents the over case - where the derived product is more free (GPL).

You seem to be right indeed:

"""3. You may opt to apply the terms of the ordinary GNU General Public=20
License instead of this License to a given copy of the Library. To do this,=
=20
you must alter all the notices that refer to this License, so that they ref=
er=20
to the ordinary GNU General Public License, version 2, instead of to this=20
License. (If a newer version than version 2 of the ordinary GNU General=20
Public License has appeared, then you can specify that version instead if y=
ou=20
wish.) Do not make any other change in these notices.=20

Once this change is made in a given copy, it is irreversible for that copy,=
 so=20
the ordinary GNU General Public License applies to all subsequent copies an=
d=20
derivative works made from that copy."""

So let's hope xmpppy bolsters a lot of high grade GPL programs. Let's hope=
=20
such programs are so good that no proprietary program could ever even start=
=20
to tempt us! :)

As someone else would say, Jabber on!

=2D-=20
Lu=EDs Marques

Re: [Xmpppy-devel] xmpppy, say hello world

[Alexey N. <sn...@pe...>]

Luis Marques wrote:

>i
>
>Ahhh... It's nice to smell the future! A fresh, new-car smelling, mailing 
>list.
>
:)) Never buyed a car. But I know how the new computer smells... It's 
amasing.

>
>By the way, about the choice of the GPL. All the Jabber clients I use are 
>licensed with the GPL. I can't imagine using a proprietary client. That said, 
>
Try JAJC. It is well designed and well written client with proprietary 
license. It is copied free but non-free since no source code comes with it.

>I'd think the LGPL is an apropriate license. I have an interest on client 
>design. Particularly easy to use clients. Not long ago I tried a proprietary 
>client. That client wasn't even a true Jabber IM client, from the user 
>perspective, in that it didn't allow to send mensagens between arbritary 
>servers. I have no interest in using it. But that client has some very 
>interesting design ideias. Had it been hindered because it had to reinvent 
>the wheel we all would loose. It's good to see new designs, that foster new 
>good ideias.
>
Yes I'm think LGPL is better for library "in general". Especially when 
_I_ go to use this library (I'm to write proprietary code due to my work 
specifics).
But... I'd prefer to loose this fifth wheel than to allow other four 
wheels go trash. I do not like closed source projects that use open 
source software.
So GPL is forces people to be free or to be non-free and not the 
combination of both.

>In any case, it's probably of little consequences, since I don't hear much 
>about proprietary Python programs. But anyway, are you sure you can take 
>existing LGPL code an re-license it under the GPL?
>
Do not sure. I have not ever read LGPL :) If you will found that this is 
illegal - leave me a note - I will replace all jabberpy code with mine.
But I am think that it is legal. Free license (LGPL) allows derived 
products to be less free than itself. I will be very surprised if it 
prevents the over case - where the derived product is more free (GPL).

--
Respectfully
Alexey Nezhdanov

[Xmpppy-devel] xmpppy, say hello world

[Luis M. <lui...@ne...>]

i

Ahhh... It's nice to smell the future! A fresh, new-car smelling, mailing=20
list.

By the way, about the choice of the GPL. All the Jabber clients I use are=20
licensed with the GPL. I can't imagine using a proprietary client. That sai=
d,=20
I'd think the LGPL is an apropriate license. I have an interest on client=20
design. Particularly easy to use clients. Not long ago I tried a proprietar=
y=20
client. That client wasn't even a true Jabber IM client, from the user=20
perspective, in that it didn't allow to send mensagens between arbritary=20
servers. I have no interest in using it. But that client has some very=20
interesting design ideias. Had it been hindered because it had to reinvent=
=20
the wheel we all would loose. It's good to see new designs, that foster new=
=20
good ideias.

In any case, it's probably of little consequences, since I don't hear much=
=20
about proprietary Python programs. But anyway, are you sure you can take=20
existing LGPL code an re-license it under the GPL?

Just my two euro cents

=2D-
Lu=EDs Marques

[Xmpppy-devel] test2

[Alexey N. <sn...@pe...>]

test2
-- 
Respectively
Alexey "Snake" Nezhdanov

[Xmpppy-devel] test

[Alexey N. <sn...@pe...>]

-- 
Respectively
Alexey "Snake" Nezhdanov