Searched refs:safe (Results 1 – 25 of 39) sorted by relevance
12
44 for safe in (2, 2.0, 2j, "abc", [3], (2,2), {3: 3}, uni("yaddayadda"),47 self.assertFalse(pprint.isrecursive(safe),48 "expected not isrecursive for %r" % (safe,))49 self.assertTrue(pprint.isreadable(safe),50 "expected isreadable for %r" % (safe,))52 self.assertFalse(pp.isrecursive(safe),53 "expected not isrecursive for %r" % (safe,))54 self.assertTrue(pp.isreadable(safe),55 "expected isreadable for %r" % (safe,))78 for safe in self.a, self.b, self.d, (self.d, self.d):[all …]
236 safe = "$-_.+"240 safe, extra, reserved)
376 result = urllib.quote(quote_by_default, safe=quote_by_default)379 result = urllib.quote_plus(quote_by_default, safe=quote_by_default)
30 if self.safe(x, y):38 def safe(self, x, y): member in Queens
180 fullurl = quote(fullurl, safe="%/:=&?~#+!$,;'@()*[]|")730 proxyhost = quote(user, safe='') + ':' + quote(passwd, safe='') + '@' + proxyhost747 proxyhost = quote(user, safe='') + ':' + quote(passwd, safe='') + '@' + proxyhost760 host = quote(user, safe='') + ':' + quote(passwd, safe='') + '@' + host773 host = quote(user, safe='') + ':' + quote(passwd, safe='') + '@' + host1213 def quote(s, safe='/'): argument1239 cachekey = (safe, always_safe)1241 (quoter, safe) = _safe_quoters[cachekey]1244 safe_map.update([(c, c) for c in safe])1246 safe = always_safe + safe[all …]
5 // The FTW protocol will not work after End Of Dxe because it will be not safe to expose
5 # The FTW protocol will not work after End Of Dxe because it will be not safe to expose
67 path_info = quote(environ.get('PATH_INFO',''),safe='/;=,')
3 # is safe for runtime use.
4 // is safe for runtime use.
60 Due to the fact that hardware-based I2C enumeration isn't safe, information
250 s = urllib.quote(s, safe='')
56 bx lr @ return (hopefully thumb-safe!)
59 * Make it safe to delete keys while iterating with the json_object_object_foreach macro.72 * Add json_object_object_get_ex(), a NULL-safe get object method, to be able
68 thread safe. We do not require thread safety because no decoder state is shared
4 thread safe. The data format used by the zlib library is described by RFCs
26 so it's also safe to invoke the callback (although that's trickier than it179 objects reachable from them, and it's safe to call them at the end of gc.
151 21. Is zlib thread-safe?154 provided memory allocation routines must also be thread-safe. zlib's gz*
122 is a known safe deviation from the Cortex-A57 TRM defined power down
140 the platform must place any secondary CPUs into a safe state while the primary