No executable installer for 3,0/3.1 about pybluez

[GoogleCodeExporter]

releasing a 3.x installer is not as simple as just rebuilding it against python 
3.x.
 python 3.x is not backwards compatible with python 2.x, and so porting pybluez to
3.x requires significant source-level changes.

you are more than welcome to contribute to this effort by submitting patches.

Original comment by [email protected] on 22 Mar 2009 at 6:17

• Changed state: Accepted
• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

yeah, I know that...and if you tell me how to fix this SDK error, I will gladly 
help.

Original comment by [email protected] on 22 Mar 2009 at 7:20

[GoogleCodeExporter]

I'd start by familiarizing yourself with this page:

http://docs.python.org/3.0/whatsnew/3.0.html

At the very bottom, there are some rough guidelines on how to go about porting 
from
2.x to 3.x (Section "Porting to Python 3.0").  That's a pretty decent guideline 
to
follow, and once you get code working, start sending patches my way.

Original comment by [email protected] on 22 Mar 2009 at 10:17

[GoogleCodeExporter]

Yeah, I've read that several times (why did they have to change it all?), but 
if I 
can't build it, I can't test it.

Probably some dependency...where would I get it?

Original comment by [email protected] on 23 Mar 2009 at 12:43

[GoogleCodeExporter]

meaning that "Can't find the Windows XP Platform SDK" is probably because of 
some 
dependency

Original comment by [email protected] on 23 Mar 2009 at 12:44

[GoogleCodeExporter]

If you do a web search for Windows XP Platform SDK, you should be able to find 
and
download it.  Once you have that installed, you'll also need a recent copy of 
Visual
Studio.  

Original comment by [email protected] on 23 Mar 2009 at 3:49

[GoogleCodeExporter]

I have VC++ Express, and was able to compile python (2.6) with it. Good enough?

Original comment by [email protected] on 23 Mar 2009 at 3:13

[GoogleCodeExporter]

Ok, got it to build. I suggest you make a svn branch for the 3.1-compatible 
code, so 
you can mess with it without breaking the 2.6 code. I'll be working on porting 
the 
python to 3.1 as best I can.

Original comment by [email protected] on 24 Mar 2009 at 7:05

[GoogleCodeExporter]

With this patch: http://paste2.org/p/170576
I was able to get: http://paste2.org/p/170569

Original comment by [email protected] on 24 Mar 2009 at 7:29

[GoogleCodeExporter]

I started the port to Python 3.1, I hope it will be released in the christmas 
holidays

Original comment by [email protected] on 2 Dec 2009 at 9:41

• Changed state: Started

[GoogleCodeExporter]

Glad to hear it :)

Original comment by [email protected] on 2 Dec 2009 at 6:34

[GoogleCodeExporter]

With this quick-and-dirty hack it compiles under Python 2.6 and Python 3.1
I only tested device scanning with msbt and widcomm and RFCOMM socket send/recv 
under 
msbt.
bluez isn't supported yet

Original comment by [email protected] on 3 Dec 2009 at 2:30

Attachments:

• py3.diff

[GoogleCodeExporter]

I've just been sent a port of the bluez portions of PyBluez to Python 3.1 and 
used it
to start a new branch.

Lukas, do you think you could integrate this patch into that branch?

Original comment by [email protected] on 11 Feb 2010 at 3:56

[GoogleCodeExporter]

I know this is a really old thread but is PyBluez for Python3 working now?

Original comment by [email protected] on 4 Jun 2012 at 10:07

[GoogleCodeExporter]

https://code.google.com/p/pybluez/downloads/list

No.

Original comment by [email protected] on 9 Jun 2012 at 2:20

[GoogleCodeExporter]

As of 3.0 : "Python 3.0 is end-of-lifed with the release of Python 
3.1"(http://python.org/download/releases/3.0.1/)

Installer for 3.1 is now included

Original comment by [email protected] on 19 Jan 2014 at 5:54

• Changed state: Fixed