Stéphane Brunet wrote:
Jim Fulton wrote:
Oh, that. Wa. Christian Theune almost had this fixed last year
at EuroPython.
This is also related to a File object refactoring that someone *almost*
finished recently.
What kind of refactoring ? Is it already in the trunk ?
No,
http://svn
Jim Fulton wrote:
Oh, that. Wa. Christian Theune almost had this fixed last year
at EuroPython.
This is also related to a File object refactoring that someone *almost*
finished recently.
What kind of refactoring ? Is it already in the trunk ?
I don't know what your solution looks lik
Stéphane Brunet wrote:
Jim Fulton wrote:
First, you are confusing schema definitions and widgets. You should
start from the definitions of the field types.
That was a typo... Sorry for the confusion :-P
As Derrick (sort of) suggested, Bytes fields are fields that contain
Python strings, a
Jim Fulton wrote:
First, you are confusing schema definitions and widgets. You should
start from the definitions of the field types.
That was a typo... Sorry for the confusion :-P
As Derrick (sort of) suggested, Bytes fields are fields that contain
Python strings, as opposed to Text fields
Stéphane Brunet wrote:
Derrick Hudson wrote:
On Sun, Jun 12, 2005 at 08:20:36PM -0400, Stéphane Brunet wrote:
[... (read the thread if you want all the background info) ...]
| What is the "raison d'être" of ASCIIWidget v.s. BytesWidget if they
| expect the same type of input (plain ASCII text
Stéphane Brunet wrote:
Derrick Hudson wrote:
On Sun, Jun 12, 2005 at 08:20:36PM -0400, Stéphane Brunet wrote:
[... (read the thread if you want all the background info) ...]
| What is the "raison d'être" of ASCIIWidget v.s. BytesWidget if they
| expect the same type of input (plain ASCII tex
Derrick Hudson wrote:
On Sun, Jun 12, 2005 at 08:20:36PM -0400, Stéphane Brunet wrote:
[... (read the thread if you want all the background info) ...]
| What is the "raison d'être" of ASCIIWidget v.s. BytesWidget if they
| expect the same type of input (plain ASCII text) and store it the same
