Peter Bengtsson wrote:
-1 on making DateTime deprecated. I'm sure thousands of zope people
use DateTime in thousands of places. Technically it might be correct
deprecate it but politically it's just going to put people off from
upgrading.
I'm sure it would be fairly trivial to write an unpgrade
Lennart Regebro wrote:
It depends on what you mena with deprecated. It *is* deprecated from
the point of view, that if you start developing something new now,
then don't use it.
Really? What should we be using instead then?
It is not deprecated in the way that "this will go away in the
future
Michael Dexter wrote:
I apologize if this is a FAQ, I could not find the answer.
I would like to put a 120MB file into ZODB and it is constantly failing.
Have a look at Tramlines from Infrae...
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://w
On 11/25/05, Chris Withers <[EMAIL PROTECTED]> wrote:
> Really? What should we be using instead then?
datetime works much better in most cases.
> I honestly think it _should_ go away, just with plenty of notice...
Well, possibly.
--
Lennart Regebro, Nuxeo http://www.nuxeo.com/
CPS Content M
Hello,
I
don't have any Python experience yet, so who has a solution for this
'problem'.
Example:
I
've 3 folders a, b & c.
I
want to create a dtml document in a folder by a form. The folder is a
variable in my form.
The formis no problem, the form action is no problem. The python
As part of an object, I have exported several zsql methods from Zope 2.2.2
and imported to Zope 2.6.2. In the later version I am using Psycopg as a
database connection to Postgres. It is working fine for all ZSQL methods I
have created within 2.6.2.
However, the methods I imported from Zope 2.2.
folder = getattr(context, 'b')
adder = folder.manage_addProduct['OFSP'].methodAdd
adder('index.html', 'Some title')
That creates it with default content. To change it you'll have to call
dtmlm = getattr(context, 'index.html')
dtmlm.manage_edit("bla bla bla bla bla", 'Same title')
# or
f = open('/t
If I have a vote, +1 on deprecation and replacement with something less
buggy. We have spent enormous amounts of time trying to sort out and then
work around DateTime problems. On the other hand, we have a substantial
amount of code that uses DateTime and finally, mostlyt works. We'd be
unhappy
--On 25. November 2005 12:22:05 -0800 Dennis Allison
<[EMAIL PROTECTED]> wrote:
If I have a vote, +1 on deprecation and replacement with something less
buggy.
You can only deprecate when you have something better. As long as there is
no useful replacemenet there is nothing to deprecate :
True. But the context of this thread was whether deprecation made sense
or not. I was agreeing with Chris that the DateTime problems are better
solved by replacement than by patching, but also that there is a large
amount of code that has been made to work using the current DataTime and
that
William Herring wrote at 2005-11-25 11:31 -0500:
> ...
>However, the methods I imported from Zope 2.2.2 do not connect to the
>database. Message is "Warning: The database connection for this method
>cannot be found!". However, the Connection ID is shown and all appears to
>be in place.
Where is
Michael Dexter wrote at 2005-11-24 11:49 -0800:
>I apologize if this is a FAQ, I could not find the answer.
>
>I would like to put a 120MB file into ZODB and it is constantly failing.
But you should have learned that you cannot simply say "is failing"
but must describe precisely (error information
--On 25. November 2005 12:43:48 -0800 Dennis Allison
<[EMAIL PROTECTED]> wrote:
True. But the context of this thread was whether deprecation made sense
or not. I was agreeing with Chris that the DateTime problems are better
solved by replacement than by patching, but also that there is a
13 matches
Mail list logo
