Message70801
| Author |
brett.cannon |
| Recipients |
brett.cannon, gvanrossum, pitrou |
| Date |
2008年08月06日.20:08:59 |
| SpamBayes Score |
0.00018840907 |
| Marked as misclassified |
No |
| Message-id |
<bbaeab100808061308k3a30dc35h6bf9f851104b2645@mail.gmail.com> |
| In-reply-to |
<1218051150.48.0.608980269909.issue3506@psf.upfronthosting.co.za> |
| Content |
On Wed, Aug 6, 2008 at 12:32 PM, Antoine Pitrou <report@bugs.python.org> wrote:
>
> Antoine Pitrou <pitrou@free.fr> added the comment:
>
> I'm no buffer API/memoryview expert, but at least slicing is not
> implemented, and there are almost no unit tests. It can probably be
> used, but given the absence of tests and of actual uses in the stdlib,
> I'm not sure we can say it is robust and therefore promote it as
> replacement.
>
Well, if it can't replace buffer() then the warning needs to change to
just flat-out state that buffer() is gone and not suggest any
replacement.
> Hopefully Travis will be able to enlighten us when he is back.
>
Hopefully. |
|