The obvious question would be why that specific, Latin 9, encoding, (which just the € sign but not a lot else), should be used. For future compatibility and widest accessability it would probably be better to use, utf-8 i.e: # -*- coding: utf-8 -*-
Last edit: GadgetSteve 2015-09-27
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have added the above utf-8 flag, and some missing #! lines to all the files in the attached zip file. Also tested with python 2.7.10 for the setup.py problem it does resolve this.
I have added the above utf-8 flag, and some missing #! lines to all the files in the attached zip file. Also tested with python 2.7.10 for the setup.py problem it does resolve this.
Cool - many thanks!
I’ve not done much on source forge for awhile … and I’ve been putting new code on github: https://github.com/nymble/cryptopyhttps://github.com/nymble/cryptopy
This does not contain all of the IEEE 802.11 stuff, so I greatly appreciate your fixes to the 1.2.5 code. I’ll just have to figure out how to get it updated.
Cool - many thanks!
I’ve not done much on source forge for awhile … and I’ve been putting
new code on github: https://github.com/nymble/cryptopy https://github.com/nymble/cryptopy
This does not contain all of the IEEE 802.11 stuff, so I greatly
appreciate your fixes to the 1.2.5 code. I’ll just have to figure out
how to get it updated.
Paul
[bugs:#6] <http://sourceforge.net/p/cryptopy/bugs/6/>
http://sourceforge.net/p/cryptopy/bugs/6/
http://www.python.org/peps/pep-0263.htmlhttp://www.python.org/peps/pep-0263.html
http://www.python.org/peps/pep-0263.html
Status: open
Group:
Labels: packaging
Created: Fri Sep 03, 2010 11:37 AM UTC by Tuomas Vesterinen
Last Updated: Sun Sep 27, 2015 07:39 AM UTC
Owner: nobody
Please add the line:
-/- coding: ISO-8859-15 -/-
to your modules.
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/cryptopy/bugs/6/
https://sourceforge.net/p/cryptopy/bugs/6/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
https://sourceforge.net/auth/subscriptions/
Status: open Group: Labels: packaging Created: Fri Sep 03, 2010 11:37 AM UTC by Tuomas Vesterinen Last Updated: Sun Sep 27, 2015 08:35 AM UTC Owner: nobody
The obvious question would be why that specific, Latin 9, encoding, (which just the € sign but not a lot else), should be used. For future compatibility and widest accessability it would probably be better to use, utf-8 i.e:
# -*- coding: utf-8 -*-Last edit: GadgetSteve 2015-09-27
I have added the above utf-8 flag, and some missing #! lines to all the files in the attached zip file. Also tested with python 2.7.10 for the setup.py problem it does resolve this.
Hi,
Cool - many thanks!
I’ve not done much on source forge for awhile … and I’ve been putting new code on github: https://github.com/nymble/cryptopy https://github.com/nymble/cryptopy
This does not contain all of the IEEE 802.11 stuff, so I greatly appreciate your fixes to the 1.2.5 code. I’ll just have to figure out how to get it updated.
Paul
Related
Bugs: #6
Paul,
I have made the same changes in a pull request on github.
Steve
On 28/09/2015 07:32, nymble wrote:
--
Steve (Gadget) Barnes
Any opinions in this message are my personal opinions and do not reflect
those of my employer.
Related
Bugs: #6