pywbem-devel — PyWBEM development related topics

Re: [pywbem-devel] Status of PyWBEM's move to GitHub

[Klaus K. <kk...@su...>]

* Andreas Maier <MA...@de...> [Oct 20. 2015 20:13]:
> 
> Hi,
> here is a short status update:
> 
> * Source code: Has been moved to GitHub under the https://github.com/pywbem
>    organisation, as five repositories. For example, the repository for the
>    PyWBEM client is: https://github.com/pywbem/pywbem.

Great, thanks for your efforts !

> 
> * Mailing list: Will stay on SourceForge. The pywbem-commit mailing list
>    there is now uninteresting, so we use only the pywbem-devel mailing list

People interested in commits can 'watch' the respective repositories
on Github.

Klaus
-- 
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

[pywbem-devel] Status of PyWBEM's move to GitHub

[Andreas M. <MA...@de...>]

Hi,
here is a short status update:

* Source code: Has been moved to GitHub under the https://github.com/pywbem
   organisation, as five repositories. For example, the repository for the
   PyWBEM client is: https://github.com/pywbem/pywbem.

* Mailing list: Will stay on SourceForge. The pywbem-commit mailing list
   there is now uninteresting, so we use only the pywbem-devel mailing list
   http://sourceforge.net/p/pywbem/mailman/pywbem-devel/ for all five
   subprojects mentioned above. The GitHub project points to the
   pywbem-devel mailing list on SourceForge.

* Bugs/Issues/Features: We use the issue tracker of each of the five
   repositories on GitHub. For example, the issue tracker for the PyWBEM
   client is: https://github.com/pywbem/pywbem/issues. The issues from the
   bug tracker on the SourceForge project are all closed and will not be
   migrated into GitHub.

* Web site: Still under way. The source files for the old web site on
   SourceForge are in the pywbem/web repo on GitHub, but they don't work
   unchanged because GitHub does not support server side scripting.

The permissions on the SourceForge project have all been closed down to
admin-only, except for the mailing list.

Pointers to the new project presence on GitHub have been set up on several
places in the SourceForge project.

With the exception of the web site, the move to GitHub is complete, and we
start working over there.

Andy

Andreas Maier
IBM Senior Technical Staff Member, OpenStack for z Systems
IBM Research & Development Laboratory Boeblingen, Germany
ma...@de..., +49-7031-16-3654

[pywbem-devel] Error werkzeug in Yawn "Exception happened ..."

[Remi C. (Imap) <rem...@gm...>]

Hi All,

When using Yawn, I get very often the following error in the logs, when 
the WSGI server Werkzeug attempts to display a static page such as a 
PNG, a js or a css:

> 127.0.0.1 - - [14/Oct/2015 21:40:58] "GET 
> /static/ui-lightness/images/logo-wbem.png HTTP/1.1" 200 -
> ----------------------------------------
> Exception happened during processing of request from ('127.0.0.1', 57387)
> Traceback (most recent call last):
>   File "C:\Python27\Lib\SocketServer.py", line 295, in 
> _handle_request_noblock
>     self.process_request(request, client_address)
>   File "C:\Python27\Lib\SocketServer.py", line 321, in process_request
>     self.finish_request(request, client_address)
>   File "C:\Python27\Lib\SocketServer.py", line 334, in finish_request
>     self.RequestHandlerClass(request, client_address, self)
>   File "C:\Python27\Lib\SocketServer.py", line 657, in __init__
>     self.finish()
>   File "C:\Python27\Lib\SocketServer.py", line 716, in finish
>     self.wfile.close()
>   File "C:\Python27\Lib\socket.py", line 283, in close
>     self.flush()
>   File "C:\Python27\Lib\socket.py", line 307, in flush
> self._sock.sendall(view[write_offset:write_offset+buffer_size])
> error: [Errno 10053] An established connection was aborted by the 
> software in your host machine
> ----------------------------------------

Example with a js javascript file:
127.0.0.1 - - [14/Oct/2015 21:39:17] "GET /static/jquery.min.js 
HTTP/1.1" 200 -
----------------------------------------
Exception happened during processing of request from ('127.0.0.1', 57295)
... same message ...

This apparently happens also in FLASK which is another Werkzeug-based 
software ( 
http://stackoverflow.com/questions/17787023/python-how-to-catch-a-flask-except-like-this 
).

It happens randomly and the result is that the document is missing.

The Werkzeug forums have nothing about this ( 
https://groups.google.com/forum/#!forum/pocoo-libs )

Do you also have this problem ?
Did you find a work around ?

Thanks

Remi

[pywbem-devel] End-to-end testing for PyWBEM client

[Andreas M. <MA...@de...>]

Hi,
I have added an approach for end-to-end testing for the PyWBEM client. This
is done by using HTTPretty to mock the HTTP communication of the client,
and to make it return HTTP responses.

The test cases for such end-to-end testing are specified as YAML files in
the testsuites/test_client directory. The new test module doing this is
testsuites/test_:client.py. There is a readme file that describes the
approach and the format of the YAML files:

https://github.com/pywbem/pywbem/tree/master/src/testsuite/test_client

and there is a demo YAML file (demo1.yaml) with one test case for a
successful GetInstance.

The goal is to use this approach for specifying testcases for all possible
CIM operations with success and failure cases. The approach allows to
specify all kinds of failures, including invalid and inconsistent HTTP
responses.

I have looked at using JSON as well, but the limitations of JSON in the
area of specifying the CIM-XMl were too severe and lead to long single-line
CIM-XML. So I gave up on it.

I'd like to invite anyone interested to comment on the approach. It takes
quite a bit to specify the test case for an operation, but I think it is
worth it.

Andy

Andreas Maier
IBM Senior Technical Staff Member, OpenStack for z Systems
IBM Research & Development Laboratory Boeblingen, Germany
ma...@de..., +49-7031-16-3654
________________________________________________________________________
IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

[pywbem-devel] PyWBEM org at GitHub changed its name from pywbem2 to pywbem

[Andreas M. <MA...@de...>]

Hi,
it turns out that it was Bart who had reserved the "pywbem" org name at
GitHub. That was good foresight!

The "pywbem2" org meanwhile has been renamed to "pywbem", so the new URL at
GitHub is:

https://github.com/pywbem - for the organisation under which you find all
five projects/repos, or:
https://github.com/pywbem/pywbem - directly for the pywbem client
project/repo.

Also, I have "inserted" the old releases of the pywbem client (0.3, 0.4,
and 0.5) that were in the releases directory, but not in the commit
history, into the commit history of the pywbem repo. That operation changes
all commit IDs. So if you already have cloned from the pywbem repo at
GitHub, you should clone again (unless you know how to deal with a changed
commit history). That is only relevant for the pywbem repo, not for any of
the other four repos.

Andy

Andreas Maier
IBM Senior Technical Staff Member, OpenStack for z Systems
IBM Research & Development Laboratory Boeblingen, Germany
ma...@de..., +49-7031-16-3654
________________________________________________________________________
IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

Re: [pywbem-devel] Moving to GitHub

[Remi C. (Imap) <rem...@gm...>]

Hi Andy


Le 06/10/2015 08:07, Andreas Maier a écrit :
>> (2) Do you think is the wbem browser Yawn, which is heavily based on
>> pywbem, will also move to github ?
> Yes, I want to move all subprojects. I was thinking that initially the
> subprojects of PyWBEM simply remain subdirectories, but if we have an
> organisation, we can easily split them out into projects under that
> organisation, over time.
I am experimenting adding Javascript to Yawn, as obviously its authors 
conveniently paved the way. And a very simple SLP browser too, as this 
is the discovery protocol for WBEM.

> At this point, CMPI providers is a topic I have not yet invested in, 
> but if there is interest, I can start digging into it. The ability to 
> write Python providers against a Python API that hooks up to CMPI as 
> an ABI sounds very interesting to me.
You might be interested by this: 
http://www.openlmi.org/3rdPartyProviders although I could not find the  
contributed providers. Also, I did not try to run one on Windows - which 
would be very convenient.



Remi

[pywbem-devel] Migrated SVN repository content to GitHub

[Andreas M. <and...@gm...>]

Hi,
I have created a pywbem2 organisation at GitHub, and migrated the SVN 
repository content from SF there:

https://github.com/pywbem2

If and when the owner of the pywbem organisation responds, we can rename 
it to pywbem, but with the pywbem2 organisation name we can at least get 
going.

The pywbem2 organisation has five subprojects, which represent the five 
subprojects we have on SF.

The commit history, and branches (we only had one special branch in the 
pyprovifc/pegasus subproject) have been migrated as well.

The committer names have been properly mapped, to the extent I had email 
addresses.

For the pywbem subproject, I created tags for the releases (That was the 
only subproject that actually had releases, afaik).

In SVN, the pyprovifc subproject had three subtrees, each of which had a 
trunk/etc directory. These three subtrees have been merged into one 
project named pyprov.

The current committers on SF are now members of the new pywbem2 
organisation, and have committer rights, including the right to create 
new projects in that organisation.

Please check out https://github.com/pywbem2 and let me know any issues 
with the migration (by posting here on the SF mailing list).

Not yet migrated is:
- mailing list
- open issues
- web presence / API documentation

Everything is still open on the Sf side, but please stay away from 
committing there.

If nobody complains about the GitHub setup until end of next week, I'll 
go ahead and close the SF repository for updates.

Andy

Re: [pywbem-devel] Status of PyWBEM 0.8.0

[Claudio K. <ck...@cl...>]

Hello Andy,

I don't know if its much of help, but I'm using 0.8.0-dev (r728)
successfully in combination with check_esxi_hardware.py (a Nagios/Icinga
plugin to monitor the hardware of VMware ESXi servers).
So far no problems at all. However the plugin (script) doesn't use all
pywbem functions, so I can't vouch for the 0.8.0 as a whole.

cheers,
ck

On Mon, Oct 5, 2015 at 6:09 PM, Andreas Maier <MA...@de...> wrote:

>
> Version 0.8.0 is basically done (except for the issues I promised to have a
> look at), but I did not test it against real CIMOMs, and therefore I'm a
> bit hesitant to just release it.
>
> It would be very helpful if people could post here if they have experience
> with the quality of the current 0.8.0 draft.
>
> Andy
>
> Andreas Maier
> IBM Senior Technical Staff Member, OpenStack for z Systems
> IBM Research & Development Laboratory Boeblingen, Germany
> ma...@de..., +49-7031-16-3654
> ________________________________________________________________________
> IBM Deutschland Research & Development GmbH
> Vorsitzende des Aufsichtsrats: Martina Koederitz
> Geschaeftsfuehrung: Dirk Wittkopp
> Sitz der Gesellschaft: Boeblingen
> Registergericht: Amtsgericht Stuttgart, HRB 243294
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> pywbem-devel mailing list
> pyw...@li...
> https://lists.sourceforge.net/lists/listinfo/pywbem-devel
>

Re: [pywbem-devel] Status of PyWBEM project

[Claudio K. <ck...@cl...>]

Thanks Andy,

Appreciate that!

cheers,
ck

On Mon, Oct 5, 2015 at 6:07 PM, Andreas Maier <MA...@de...> wrote:

>
> Hi,
> in response to a post from June: The PyWBEM project is not dead, but I did
> not find much time to work on it.
>
> I'll look into the proposed changes.
>
> See my next post on the move to GitHub.
>
> Andy
>
> Andreas Maier
> IBM Senior Technical Staff Member, OpenStack for z Systems
> IBM Research & Development Laboratory Boeblingen, Germany
> ma...@de..., +49-7031-16-3654
> ________________________________________________________________________
> IBM Deutschland Research & Development GmbH
> Vorsitzende des Aufsichtsrats: Martina Koederitz
> Geschaeftsfuehrung: Dirk Wittkopp
> Sitz der Gesellschaft: Boeblingen
> Registergericht: Amtsgericht Stuttgart, HRB 243294
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> pywbem-devel mailing list
> pyw...@li...
> https://lists.sourceforge.net/lists/listinfo/pywbem-devel
>

Re: [pywbem-devel] Moving to GitHub

[Claudio K. <ck...@cl...>]

Yes, keep mailing list please. I don't care which provider you use but
don't "move" it into a forum or Stackoverflow or something like this.
Had a very bad experience with such a "move" from the nagios mailing list
into a web forum... :(

On Tue, Oct 6, 2015 at 8:39 AM, Klaus Kaempf <kk...@su...> wrote:

> * Andreas Maier <MA...@de...> [Oct 05. 2015 18:09]:
> >
> >    - Mailing list: TBD. I'm up for good ideas on that. Options might be:
> >       - No need, we can do it via StackOverflow
> >       - Continue with SourceForge mailing list
> >       - Google Groups
> >       - Use some other mailing list /forum provider (ideas about which
> >       one?)
> >
>
> My take on that topic: If it ain't broke, don't fix it.
>
> I moved Openwsman from sourceforge to github years ago and left the
> mailing lists in place. Works perfectly.
>
> Klaus
> --
> SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB
> 21284 (AG Nürnberg)
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> pywbem-devel mailing list
> pyw...@li...
> https://lists.sourceforge.net/lists/listinfo/pywbem-devel
>

[pywbem-devel] Moving to GitHub

[Andreas M. <MA...@de...>]

Hi Remi,
inline.

Andy

"Remi Chateauneu (Imap)" <rem...@gm...> wrote on 05.10.2015
23:57:41:
>
> (1) For your information, there is on GitHub a project which started to
> port pywbem to Python 3:
>
> https://github.com/deejross/python3-pywbem
>
> Maybe this project will redefine itself as a pywbem fork which would be
> convenient.

I just stumbled across this project just now. At this point, it has just
the source doe of the pywbem client, without its test subdirectory, and
without the other subprojects.

I wanted to have the new pywbem project on GitHub with a URL independent
of a single user. GitHub offers the concept of organisations, and I have
used that for another project (CMPI documentation). However, it turns
out that the organisation name "pywbem" is already taken on GitHub,
with no public users and with no repositories. I suppose (hope) that
someone has created that in preparation of a move of our PyWBEM to
GitHub.

If that somebody listens here: Please get in contact with me
(maiera at de dot ibm dot com), to discuss whether we can use that
org for PyWBEM.

> (2) Do you think is the wbem browser Yawn, which is heavily based on
> pywbem, will also move to github ?

Yes, I want to move all subprojects. I was thinking that initially the
subprojects of PyWBEM simply remain subdirectories, but if we have an
organisation, we can easily split them out into projects under that
organisation, over time.

> (3) "documentation for the pywbem subproject "
>
> Will there be documentation about CMPI providers in Python ? And ideally
> not only on Linux ? For example the registering architecture is not
> completely clear.

What I can produce relatively easily is the API documentation for the
pywbem
client. the source code has already been improved quite a bit with up to
date docstrings, it is just a matter of getting the publication process to
work.

At this point, CMPI providers is a topic I have not yet invested in, but if
there
is interest, I can start digging into it. The ability to write Python
providers
against a Python API that hooks up to CMPI as an ABI sounds very
interesting
to me.

> Thanks for everything, pywbem is a great tool.

:-)

I really want to get the community going somewhat more and realize that
having
not been around for months is not a good thing. I have only so much time
for side projects, and helping to get CMPI 2.1 out the door kept me pretty
busy.

Andy

Re: [pywbem-devel] Moving to GitHub

[Klaus K. <kk...@su...>]

* Andreas Maier <MA...@de...> [Oct 05. 2015 18:09]:
> 
>    - Mailing list: TBD. I'm up for good ideas on that. Options might be:
>       - No need, we can do it via StackOverflow
>       - Continue with SourceForge mailing list
>       - Google Groups
>       - Use some other mailing list /forum provider (ideas about which
>       one?)
> 

My take on that topic: If it ain't broke, don't fix it.

I moved Openwsman from sourceforge to github years ago and left the
mailing lists in place. Works perfectly.

Klaus
-- 
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

Re: [pywbem-devel] Moving to GitHub

[Remi C. (Imap) <rem...@gm...>]

Le 05/10/2015 17:08, Andreas Maier a écrit :
> I had a discussion with the current maintainers about moving the project to
> GitHub, and the idea was generally appreciated; and nobody was opposed.

Hi Andreas,

(1) For your information, there is on GitHub a project which started to 
port pywbem to Python 3:

https://github.com/deejross/python3-pywbem

Maybe this project will redefine itself as a pywbem fork which would be 
convenient.

(2) Do you think is the wbem browser Yawn, which is heavily based on 
pywbem, will also move to github ?

(3) "documentation for the pywbem subproject "

Will there be documentation about CMPI providers in Python ? And ideally 
not only on Linux ? For example the registering architecture is not 
completely clear.

Thanks for everything, pywbem is a great tool.

Remi

>

[pywbem-devel] Moving to GitHub

[Andreas M. <MA...@de...>]

I had a discussion with the current maintainers about moving the project to
GitHub, and the idea was generally appreciated; and nobody was opposed.

The proposal for the migration is as follows:

   - Create a single repository on GitHub with the current subdirectory
      tree from SourceForge. This will include SVN-typical directories such
      as trunk, branches, etc.  that we have for each of the subprojects of
      PyWBEM currently. The original userids of each commit will be mapped
      and thus retained. I was able to dig out most userid, except for some
      commits very early in the project.

   - The bugs on SourceForge that are open at this point, will be recreated
   (by me) on the GitHub issue tracker.

   - The SourceForge web site for PyWBEM will be moved to the wiki of the
   GitHub project.

   - Mailing list: TBD. I'm up for good ideas on that. Options might be:
      - No need, we can do it via StackOverflow
      - Continue with SourceForge mailing list
      - Google Groups
      - Use some other mailing list /forum provider (ideas about which
      one?)

After the migration, the following work would be up:

   - Shape out the source tree to be more like a normal GitHub project. The
      subprojects would still stay in separate directory trees for the time
      being.

   - Create API documentation for the pywbem subproject somewhere (either
      on readthedocs, or on GitHub:pages). I took a first stab at using
      Sphinx.

Comments are welcome!

Andy

Andreas Maier
IBM Senior Technical Staff Member, OpenStack for z Systems
IBM Research & Development Laboratory Boeblingen, Germany
ma...@de..., +49-7031-16-3654
________________________________________________________________________
IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

[pywbem-devel] Status of PyWBEM project

[Andreas M. <MA...@de...>]

Hi,
in response to a post from June: The PyWBEM project is not dead, but I did
not find much time to work on it.

I'll look into the proposed changes.

See my next post on the move to GitHub.

Andy

Andreas Maier
IBM Senior Technical Staff Member, OpenStack for z Systems
IBM Research & Development Laboratory Boeblingen, Germany
ma...@de..., +49-7031-16-3654
________________________________________________________________________
IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

[pywbem-devel] Status of PyWBEM 0.8.0

[Andreas M. <MA...@de...>]

Version 0.8.0 is basically done (except for the issues I promised to have a
look at), but I did not test it against real CIMOMs, and therefore I'm a
bit hesitant to just release it.

It would be very helpful if people could post here if they have experience
with the quality of the current 0.8.0 draft.

Andy

Andreas Maier
IBM Senior Technical Staff Member, OpenStack for z Systems
IBM Research & Development Laboratory Boeblingen, Germany
ma...@de..., +49-7031-16-3654
________________________________________________________________________
IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

[pywbem-devel] Python providers on Windows

[Remi C. <rem...@gm...>]

Hi,

I would like to run Python providers on Windows with OpenPegasus.

The method on Linux is apparently to install and register the
shareable library libpyCmpiProvider.so  to the CIMOM as a provider
module. And
once it is done, any Python script copied in the right location, is
detected and acts as a WBEM provider.

If OpenPegasus on Windows is compiled with the CMPI option
(Which is not the default btw), do you think it is feasible to port to
Windows, the source code of libpyCmpiProvider, that is, the RPM
cmpi-bindings-0.9.5-6.el7.src ? With MinGW maybe ?

Otherwise, is there another binding library on Windows, to run Python
providers ?

Thanks

Remi

[pywbem-devel] Installing Python providers with OpenPegasus and Pywbem

[Remi C. <rem...@gm...>]

Hi,

Is there any documentation on how to register Python providers with
OpenLMI or OpenPegasus ? Simple examples (Ideally on Windows) ?

Thanks

Remi

Re: [pywbem-devel] 0.8 status check

[Claudio K. <ck...@cl...>]

http://sourceforge.net/p/pywbem/bugs/?source=navbar

On Wed, Jun 10, 2015 at 11:29 PM, Remi Chateauneu <rem...@gm...
> wrote:

> No idea, I am new on this list.
>
> Where is the documentation about these bugs please ?
>
> Thanks
>
> Remi
>
> On 6/10/15, Claudio Kuenzler <ck...@cl...> wrote:
> > Hello list,
> >
> > I sincerely hope that the pywbem project is not dead (again)?
> > Any news about a final 0.8 release?
> >
> > The last update on the website is from January and the (currently) two
> bugs
> > haven't seen an update from an upstream maintainer in a while.
> >
> > Thanks,
> > Claudio
> >
>

Re: [pywbem-devel] 0.8 status check

[Remi C. <rem...@gm...>]

No idea, I am new on this list.

Where is the documentation about these bugs please ?

Thanks

Remi

On 6/10/15, Claudio Kuenzler <ck...@cl...> wrote:
> Hello list,
>
> I sincerely hope that the pywbem project is not dead (again)?
> Any news about a final 0.8 release?
>
> The last update on the website is from January and the (currently) two bugs
> haven't seen an update from an upstream maintainer in a while.
>
> Thanks,
> Claudio
>

[pywbem-devel] 0.8 status check

[Claudio K. <ck...@cl...>]

Hello list,

I sincerely hope that the pywbem project is not dead (again)?
Any news about a final 0.8 release?

The last update on the website is from January and the (currently) two bugs
haven't seen an update from an upstream maintainer in a while.

Thanks,
Claudio

Re: [pywbem-devel] "python 3 support" for Yawn

[Remi C. <rem...@gm...>]

By the way, has someone any information about the WMI Mapper project
which is part of OpenPegasus (In a way related to pywbem) ? It does
not compile and there does not seem to be much progress on it.

Thanks

Remi

On 4/10/15, Michal Minář <mi...@re...> wrote:
> Great news! Recently I'm occupied by another project so
> I don't have any time to port yawn myself.
>
> It would be great if the author could propose his changes
> upstream.
>
> Best regards,
> Michal
>
> On 9.4.2015 08:52, Remi Chateauneu wrote:
>> Hi All,
>>
>> I just read in the file yawn\trunk\mod_wsgi\TODO the line:
>>
>> python 3 support
>>
>> Are you aware of this project which intends to port PyWbem on Python 3 ?
>>
>> https://github.com/deejross/python3-pywbem
>>
>> "This is a fork of PyWBEM for Python 2.6+ and Python 3.4+"
>>
>> Hope it helps
>>
>> Remi
>>
>> ------------------------------------------------------------------------------
>> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
>> Develop your own process in accordance with the BPMN 2 standard
>> Learn Process modeling best practices with Bonita BPM through live
>> exercises
>> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
>> event?utm_
>> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
>> _______________________________________________
>> pywbem-devel mailing list
>> pyw...@li...
>> https://lists.sourceforge.net/lists/listinfo/pywbem-devel
>>
>
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live
> exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> pywbem-devel mailing list
> pyw...@li...
> https://lists.sourceforge.net/lists/listinfo/pywbem-devel
>

[pywbem-devel] Python 3 Support

[Ross P. <ros...@gm...>]

Hello,

A couple of months ago, I downloaded the latest PyWBEM release and
discovered that it lacked Python 3 support, so I updated the code base to
support Python 2.6+ and Python 3.4+. I posted the code to GitHub and have
since been asked to try and get a conversation going with upstream to get
my changes merged in.

I am not subscribed to this group directly, so please email me directly,
but here are the appropriate links:

The request/issue opened on GitHub:
https://github.com/deejross/python3-pywbem/issues/2#issuecomment-91534715

The project source:
https://github.com/deejross/python3-pywbem

Please let me know if you are interested in getting my changes added to
your code base and I will help where I can.

Thank you,

Ross

Re: [pywbem-devel] "python 3 support" for Yawn

[Michal M. <mi...@re...>]

Great news! Recently I'm occupied by another project so
I don't have any time to port yawn myself.

It would be great if the author could propose his changes
upstream.

Best regards,
Michal

On 9.4.2015 08:52, Remi Chateauneu wrote:
> Hi All,
>
> I just read in the file yawn\trunk\mod_wsgi\TODO the line:
>
> python 3 support
>
> Are you aware of this project which intends to port PyWbem on Python 3 ?
>
> https://github.com/deejross/python3-pywbem
>
> "This is a fork of PyWBEM for Python 2.6+ and Python 3.4+"
>
> Hope it helps
>
> Remi
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> pywbem-devel mailing list
> pyw...@li...
> https://lists.sourceforge.net/lists/listinfo/pywbem-devel
>

[pywbem-devel] "python 3 support" for Yawn

[Remi C. <rem...@gm...>]

Hi All,

I just read in the file yawn\trunk\mod_wsgi\TODO the line:

python 3 support

Are you aware of this project which intends to port PyWbem on Python 3 ?

https://github.com/deejross/python3-pywbem

"This is a fork of PyWBEM for Python 2.6+ and Python 3.4+"

Hope it helps

Remi