On 10 October 2014 02:29, Victor Stinner victor.stin...@gmail.com wrote:
The free version (Visual Studio Express) only supports 32-bit
VC++ 2008/2010 EE do not *bundle* a 64-bit compiler, but it's certainly
possible to build 64-bit applications by using the compiler in the (also
free) Windows
On 13 March 2012 20:43, VanL van.lindb...@gmail.com wrote:
Following up on conversations at PyCon, I want to bring up one of my
personal hobby horses for change in 3.3: Fix install layout on Windows, with
a side order of making the PATH work better.
As this is being considered an 'incompatible
On 17 March 2012 00:57, Guido van Rossum gu...@python.org wrote:
OK, how about using encoding=bytes (yes, the type object!)? Or 'bytes' ?
encoding=bytes makes (at least intuitive) sense to me;
encoding='bytes' would imply there is an encoding with name 'bytes'
that somehow does
On 17 March 2012 10:43, Stefan Behnel stefan...@behnel.de wrote:
In lxml, there was an encoding=unicode option that would let the
XML/HTML/text serialisation function return a Unicode string. This was
eventually deprecated in favour of encoding='unicode' when ElementTree
gained this feature as
On 17 March 2012 16:28, Serhiy Storchaka storch...@gmail.com wrote:
Thus, there are no reasons to use bytes instead of 'bytes'.
Aesthetics ;-)
I've implemented the encoding=bytes version [1]. Thank you all for your input!
Merlijn
[1] http://bugs.python.org/issue6784#msg156166
Hi Guido,
Let me start with thanking you for your long reply. It has clarified
some points to me, but I am still not certain about some others. I
hope I can clarify why I'm confused about this issue in the following.
First of all, let me clarify that I wrote my original mail not as 'the
guy who
http://bugs.python.org/issue6784 (byte/unicode pickle
incompatibilities between python2 and python3)
Hello all,
Currently, pickle unpickles python2 'str' objects as python3 'str'
objects, where the encoding to use is passed to the Unpickler.
However, there are cases where it makes more sense to
Oops. I should re-read my mails before I send them, not /after/ I send them.
On 13 March 2012 12:44, Merlijn van Deen valhall...@arctus.nl wrote:
pickled = BytestrPickler(data, bytestr=True); unpickled =
BytestrUnpickler(data, bytestr=True)
should of course read
pickled = BytestrPickler
On 13 March 2012 22:13, Guido van Rossum gu...@python.org wrote:
Well, since trying to migrate data between versions using pickle is
the wrong thing anyway, I think the status quo is just fine.
Developers doing the right thing don't use pickle for this purpose.
I'm confused by this. The pickle
On 1 March 2012 12:11, Stefan Krah ste...@bytereef.org wrote:
Advantages of separate branches:
Even though I agree on most of your points, I disagree with
2) Neither version is a second class citizen.
In my experience, this is only true if you have a very strict discipline,
or if both
10 matches
Mail list logo
