> Or perhaps make it emit DeprecationWarnings, but continue working. Then
> make it a fatal error in the next minor/major release.
>
+1
Pedro
--
José Pedro Ferreira
Indico Team
IT-UDS-AVC
513-R-0042
CERN, Geneva, Switzerland
___
For more inf
On 25/10/2010 23:34, Marius Gedminas wrote:
> Or perhaps make it emit DeprecationWarnings, but continue working. Then
> make it a fatal error in the next minor/major release.
Well, not a DeprecationWarning... Is there a DataLossWarning?
Still, +1 on the warning followed by exception in 2 release
Hi,
In order to scale an application using RelStorage I was thinking about
seperating reads and writes accross databases. Writes would go to a Mysql
master and the app would read from one or more Mysql slaves.
It looks like RelStorage already keeps seperate connections for read and
write (even th
On 10/26/2010 04:04 AM, Anton Stonor wrote:
> In order to scale an application using RelStorage I was thinking about
> seperating reads and writes accross databases. Writes would go to a
> Mysql master and the app would read from one or more Mysql slaves.
If you mean that you intend to set up some
Hi Shane,
In order to scale an application using RelStorage I was thinking about
>> seperating reads and writes accross databases. Writes would go to a
>> Mysql master and the app would read from one or more Mysql slaves.
>>
>
> If you mean that you intend to set up some clients to write to a ma
On Mon, Oct 25, 2010 at 6:34 PM, Marius Gedminas wrote:
...
> Or perhaps make it emit DeprecationWarnings, but continue working. Then
> make it a fatal error in the next minor/major release.
I like this idea. I think I'm going to use UserWarning because it isn't
disabled in Python 2.7 afaik. O
