FilesExpand file tree

 3.6

/

objbuffer.po

Copy path

Blame

More file actions

Blame

More file actions

Latest commit

 

History

History

History

101 lines (94 loc) · 4.74 KB

 3.6

/

objbuffer.po

Copy path

Top

File metadata and controls

• Code
• Blame

101 lines (94 loc) · 4.74 KB

Raw

Copy raw file

Download raw file

Open symbols panel

Edit and raw actions

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

70

71

72

73

74

75

76

77

78

79

80

81

82

83

84

85

86

87

88

89

90

91

92

93

94

95

96

97

98

99

100

101

# SOME DESCRIPTIVE TITLE.

# Copyright (C) 2001-2016, Python Software Foundation

# This file is distributed under the same license as the Python package.

# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.

#

#, fuzzy

msgid ""

msgstr ""

"Project-Id-Version: Python 3.6\n"

"Report-Msgid-Bugs-To: \n"

"POT-Creation-Date: 2017-04-02 22:11+0200\n"

"PO-Revision-Date: 2018-01-29 00:24+0100\n"

"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"

"Language-Team: LANGUAGE <LL@li.org>\n"

"Language: fr\n"

"MIME-Version: 1.0\n"

"Content-Type: text/plain; charset=UTF-8\n"

"Content-Transfer-Encoding: 8bit\n"

#: ../Doc/c-api/objbuffer.rst:4

msgid "Old Buffer Protocol"

msgstr "Ancien *Buffer Protocol*"

#: ../Doc/c-api/objbuffer.rst:8

msgid ""

"These functions were part of the \"old buffer protocol\" API in Python 2. In "

"Python 3, this protocol doesn't exist anymore but the functions are still "

"exposed to ease porting 2.x code. They act as a compatibility wrapper "

"around the :ref:`new buffer protocol <bufferobjects>`, but they don't give "

"you control over the lifetime of the resources acquired when a buffer is "

"exported."

msgstr ""

"Ces fonctions faisaient partie de l'API de l'ancien protocole de tampons "

"dans Python 2. Dans Python 3, ce protocole n'existe plus, mais les fonctions "

"sont toujours exposées pour simplifier le portage de code Python 2.x. Elles "

"se comportent comme une abstraction de compatibilité du :ref:`nouveau "

"protocole de tampons <bufferobjects>`, mais sans vous donner de contrôle sur "

"la durée de vie des ressources acquises lorsqu'un tampon est exporté."

#: ../Doc/c-api/objbuffer.rst:15

msgid ""

"Therefore, it is recommended that you call :c:func:`PyObject_GetBuffer` (or "

"the ``y*`` or ``w*`` :ref:`format codes <arg-parsing>` with the :c:func:"

"`PyArg_ParseTuple` family of functions) to get a buffer view over an object, "

"and :c:func:`PyBuffer_Release` when the buffer view can be released."

msgstr ""

"Il est donc recommandé d'appeler :c:func:`PyObject_GetBuffer` (ou les :ref:"

"`codes <arg-parsing>` ``y*`` ou ``w*`` à la famille de fonctions :c:func:"

"`PyArg_ParseTuple`) pour obtenir une vue d'un tampon sur un objet, et :c:"

"func:`PyBuffer_Release` lorsque la vue peut être libérée."

#: ../Doc/c-api/objbuffer.rst:23

msgid ""

"Returns a pointer to a read-only memory location usable as character-based "

"input. The *obj* argument must support the single-segment character buffer "

"interface. On success, returns ``0``, sets *buffer* to the memory location "

"and *buffer_len* to the buffer length. Returns ``-1`` and sets a :exc:"

"`TypeError` on error."

msgstr ""

"Retourne un pointeur vers un emplacement de mémoire en lecture seule "

"utilisable en tant qu'entrée basée sur des caractères. L'argument *obj* doit "

"prendre en charge l'interface de tampon de caractère à segment unique. En "

"cas de succès, retourne ``0``, définit *buffer* à l'emplacement de la "

"mémoire et *buffer_len* à la longueur de la mémoire tampon. Retourne ``-1`` "

"et affecte une exception :exc:`TypeError` en cas d'erreur."

#: ../Doc/c-api/objbuffer.rst:32

msgid ""

"Returns a pointer to a read-only memory location containing arbitrary data. "

"The *obj* argument must support the single-segment readable buffer "

"interface. On success, returns ``0``, sets *buffer* to the memory location "

"and *buffer_len* to the buffer length. Returns ``-1`` and sets a :exc:"

"`TypeError` on error."

msgstr ""

"Retourne un pointeur vers un emplacement de mémoire en lecture seule "

"contenant des données arbitraires. L'argument *obj* doit prendre en charge "

"l'interface de tampon lisible à segment unique. En cas de succès, retourne "

"``0``, définit *buffer* à l'emplacement de la mémoire et *buffer_len* à la "

"longueur de la mémoire tampon. Renvoie ``-1`` et affecte l'exception :exc:"

"`TypeError` en cas d'erreur."

#: ../Doc/c-api/objbuffer.rst:41

msgid ""

"Returns ``1`` if *o* supports the single-segment readable buffer interface. "

"Otherwise returns ``0``."

msgstr ""

"Renvoie ``1`` si *o* gère l'interface *single-segment readable buffer*, "

"``0`` sinon."

#: ../Doc/c-api/objbuffer.rst:47

msgid ""

"Returns a pointer to a writable memory location. The *obj* argument must "

"support the single-segment, character buffer interface. On success, returns "

"``0``, sets *buffer* to the memory location and *buffer_len* to the buffer "

"length. Returns ``-1`` and sets a :exc:`TypeError` on error."

msgstr ""

"Renvoie un pointeur vers un espace mémoire dans lequel il est possible "

"décrire. L'argument *obj* doit gérer l'interface *single-segment, character "

"buffer*. Si tout s'est bien passé, ``0`` est renvoyé, *buffer* pointe vers "

"l'espace mémoire, et *buffer_len* vaudra la taille du tampon. Renvoie ``-1`` "

"et met l'exception :exc:`TypeError` en cas d'erreur."