repeated from c.l.p : "Feature Request: Py_NewInterpreter to create
separate GIL (branch)"
Daniel Dittmar wrote:
> robert wrote:
>> I'd like to use multiple CPU cores for selected time consuming Python
>> computations (incl. numpy/scipy) in a frictionles
n
Py3K).
Py_FASTINCREF could be fast for known immutables (mainly Py_None) with MAXINT
method, and for fresh creations etc.
PyThreadState_GET(): A ts(PyThread_get_thread_ident())/*TlsGetValue() would
become necessary. Is there a fast thread_ID register in todays CPU's?*
Robert
___
k):
how-to-yield-from-here-as-iter_retr blk???
self.ftp.retrbinary("RETR %s" % self.relpath,callback)
def read(self, bytes=-1):
...
self.buf+=self.iter.next()
...
...
=
Robert
___
st when working with trees on the scale of a full Fedora or RHEL
> build hosted on an NFS share).
>
> Cheers,
> Nick.
>
> --
> Nick Coghlan | [email protected] | Brisbane, Australia
> ___
> Python-Dev mailing list
>
Indeed - my suggestion is applicable to people using the library
-Rob
On 10 Aug 2014 18:21, "Larry Hastings" wrote:
> On 08/09/2014 10:40 PM, Robert Collins wrote:
>
> A small tip from my bzr days - cd into the directory before scanning it
>
>
> I doubt that
moderated,
so...
Bill"
- nothing to see here, move right along, and sorry for the noise.
-Rob
On 21 September 2014 10:19, Robert Collins wrote:
> I'm not sure of the right place to bring this up - I tried to on the
> web-sig list itself, but the moderator rejected the post.
>
ard: can we get that changed (or
is there some historical need for it - if so, perhaps we should use
python-dev or some other list) ?"""
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
___
Python-Dev mailing list
Python-Dev
On 9 February 2015 at 09:11, Maciej Fijalkowski wrote:
> Hi Francis
>
> Feel free to steal most of vmprof code, it should generally work
> without requiring to patch cpython (python 3 patches appreciated :-).
> As far as timer goes - it seems not to be going anywhere, I would
> rather use a backgr
cts makes checking back on them later easier, should we need to.
One question, if you will - I don't think this was asked so far - is
authenticode verifiable from Linux, without Windows? And does it work
for users of WINE ?
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged C
e name of the package to
process.
Since discovery is recursive, sub namespace packages should work, but
I note there are no explicit tests to this effect.
I'm sorry I didn't respond earlier on the tracker, didn't see the
issue in my inbox for some
ntly break, but that seems like a fairly shallow bug to
me, rather than something that shouldn't work. The advantage of that
route is that editors which make comments appear in subtle colours,
makes the type hints be unobtrusive without specific syntax colouring
support.
-Rob
--
Robert
atic analysis instead of the actual source. Likely I've got it
modelled wrong in my head :)
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman
ts the fundamental design. Stubs don't annotate python code,
they *are* annotated code themselves. They aren't merged with the
observed code at all.
Could they be? Possibly. I don't know how much work that would be.
-Rob
--
Robert Collins
Distinguishe
rently seeing stubs as a necessary *evil*
> they're missing points where they're a better backwards compatible solution
> for people who want to give users with capable IDEs the ability to use stub
> (or hint) files.
-Rob
--
Robert Collins
Distinguished Technologist
HP Conver
st. (The
> type checker would be responsible for pointing out bugs. :-P )
What about major changes to existing modules? I have a backlog of
intended feature uplifts from testtools into unittest - if the type
hints thing works out I am likely to put them into testtools. Whats
your view on type hint
ols, traceback2,
linecache2) to get something small enough to work and experiment with.
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/list
bash fun was very good evidence of that.
OTOH if someones environment is at risk, PATH and PYTHONPATH are
already very effective attack vectors.
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
___
Python-Dev mailing list
Python-Dev@py
be clear, I don't mean that using the built
> in ssl module APIs to disable verification should raise a warning, I mean the
> hypothetical "make my Python insecurely access HTTPS" configuration file (or
> environment variable) that is being proposed.
>
> ---
> Donald Stufft
&g
Plus 1 from me. I'm not 100% sure the signature / inspect backport does
this, but as you say, it should be trivial to do, to whatever extent the
python version we're hosted on does it.
Rob
On 28 Nov. 2017 07:14, "Larry Hastings" wrote:
>
>
> First, a thirty-second refresher, so we're all using
As requested on the bug tracker, I've submitted a pull request for
is_integer() support on the other numeric types.
https://github.com/python/cpython/pull/6121
These are the tactics I used to implement it:
- float: is_integer() already exists, so no changes
- int: return True
- Real: return x
Here's an excerpted (and slightly simplified for consumption here) usage of
float.is_integer() from the top of a function which does some
convolution/filtering in a geophysics application. I've mostly seen it used
in guard clauses in this way to reject either illegal numeric arguments
directly, or
argument that a putative complex.is_integral() should
therefore return False, but I expect that would get even less support than
the other suggestions in these threads.
*Robert Smallshire | *Managing Director
*Sixty North* | Applications | Consulting | Training
[email protected] | T +47 63 01 04 44 | M +47
e existence of
>>>> dec_mpd_isinteger() seems to validate to me that it actually exposes useful
>>>> functionality (and every Python feature can be abused, so that alone should
>>>> not
>>>>
>>> )
>>
> ___
One question..
On Thu., 29 Mar. 2018, 07:42 Antoine Pitrou, wrote:
> ...
>
===
>
> Mutability
> --
>
> PEP 3118 buffers [#pep-3118]_ can be readonly or writable. Some objects,
> such as Numpy arrays, need to be backed by a mutable buffer for full
> operation. Pickle consumers that
ymbols, operators or keywords, are
consistent with existing usage, and address two relatively common causes of
displeasing Python code.
Robert
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscri
se it'd be a nice to split this up, as well as
unify normal-method and c-defined-method if that's palatable).
- Robert
On Mon, Apr 30, 2018 at 8:55 AM, Jeroen Demeyer wrote:
> On 2018-04-30 15:38, Mark Shannon wrote:
>
>> While a unified *interface* makes sens
compatibility concerns if taken as far as possible.)
- Robert
On Sun, May 20, 2018 at 1:15 PM, Jeroen Demeyer wrote:
> On 2018-05-19 15:29, Nick Coghlan wrote:
>>
>> That's not how code reviews work, as their complexity is governed by the
>> number of lines changed (added
gt; create a bunch of make-work for everybody?
>
> Monitoring the progress of our experiment,
When I next get tuits, it will be on 3.6; I like the branch early even
though I haven't used it.
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
_
tly.
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/arch
retty much every OpenStack project got git
with it when I released mock 1.1).
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubs
On 14 July 2015 at 14:25, R. David Murray wrote:
> On Tue, 14 Jul 2015 14:01:25 +1200, Robert Collins
> wrote:
>> So unittest.mock regressed during 3.5, and I found out when I released
>> the mock backport.
>>
>> The regression is pretty shallow - I've applied
ltimately I'm +1 on reserving "assert" (given that a more radical
> fix isn't possible) and +0 on adding "assret" (simply on the basis
> that someone more knowledgeable than me says it makes sense).
Since assret is solely a 'you may not use this' case, I think
On 15 July 2015 at 07:39, Paul Moore wrote:
> On 14 July 2015 at 20:27, Robert Collins wrote:
>>> In effect, this patch is "reserving" all attributes starting with
>>> "assert" or "assret" as actual methods of the mock object, and not
>&g
such things.
It can't, but there is a sliding scale of API usability, and we should
try to be up the good end of that :).
http://sweng.the-davies.net/Home/rustys-api-design-manifesto
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
__
On 15 July 2015 at 10:05, Ethan Furman wrote:
> On 07/14/2015 02:53 PM, Robert Collins wrote:
...
>>> I don't think unittest can protect its users from such things.
>>
>>
>> It can't, but there is a sliding scale of API usability, and we should
>>
On 15 July 2015 at 15:00, Stephen J. Turnbull wrote:
> Robert Collins writes:
>
> > What I am doing is rejecting the argument that because we can't fix
> > every mis-use users might make, we therefore should not fix the cases
> > where we can fix it.
>
> Th
On 15 July 2015 at 12:59, Nick Coghlan wrote:
>
> There is zero urgency here, so nothing needs to change for 3.5.
> Robert's plan is a fine one to propose for 3.6 (and the PyPI mock
> backport).
Right - the bad API goes back to the very beginning. I'm not planning
on writing the new thing I sketc
On 15 July 2015 at 19:17, Antoine Pitrou wrote:
> On Wed, 15 Jul 2015 10:22:14 +1200
> Robert Collins wrote:
>>
>> For clarity, I think we should:
>> - remove the assret check, it is I think spurious.
>> - add a set of functions to the mock module that shou
On 17 Jul 2015 08:34, "Michael Foord" wrote:
>
>
>
> On Wednesday, 15 July 2015, Robert Collins
wrote:
> > On 15 July 2015 at 12:59, Nick Coghlan wrote:
> >>
> >> There is zero urgency here, so nothing needs to change for 3.5.
> >> Rober
hich case open a new ticket at
https://bugs.python.org/ linked to the github issue, and either close
the github issue or label it upstream (or both)).
THAT would be valuable, and improve users experience of unittest.mock
[and mock] much more than making a_mock.assret_called_once *not
error*.
for PYthon core committers?
What's the goal here: what actual problem are we trying to solve for?
More contributors? A better Python more people can use? Keeping up
with the contributions we've already received but not actioned? [...]
Like: pick one thing. What we /really/ want to achie
On 21 July 2015 at 19:40, Nick Coghlan wrote:
> On 20 July 2015 at 22:34, Ben Finney wrote:
>> Paul Moore writes:
>>
>>> Again, I'm sorry to pick on one sentence out of context, but it cut
>>> straight to my biggest fear when doing a commit (on any project) -
>>> what if, after all the worrying
e his solution,
> but if not, you could open one and add him as nosy.
I did: http://bugs.python.org/issue24651
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
___
Python-Dev mailing list
[email protected]
https://
hon.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/robertc%40robertcollins.net
>
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
___
P
On 22 July 2015 at 05:08, Larry Hastings wrote:
>
>
> On 07/21/2015 06:35 PM, Robert Collins wrote:
>
> Cool. http://bugs.python.org/issue21750 is in a bad state right now.
>
> I landed a patch to fix it, which when exposed to users had some
> defects. I'm working on
On 22 July 2015 at 08:07, Robert Collins wrote:
> On 22 July 2015 at 05:08, Larry Hastings wrote:
>>
>>
>> On 07/21/2015 06:35 PM, Robert Collins wrote:
>>
>> Cool. http://bugs.python.org/issue21750 is in a bad state right now.
>>
>> I landed a pat
iew it, but I think it would be great if other committers were to
also to do this: if we had 5 of us doing 1 a day, I think we'd burn
down this 45 patch backlog rapidly without significant individual
cost. At which point, we can fairly say to folk doing triage that
we're ready for patche
claim such entitlement, who does? Whose entitlement are
you arguing for? If its Guido's, I think we can stop arguing - sure,
he is entitled to ask for a lot, but I don't want to argue about what
entitlements someone else has: they can argue on their own.
-Rob
--
Robert Collins
Distinguish
ad to folk having a poorer
experience.
Is this a simple bug, or do we need to update the PEP?
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listi
> ensurepip bundle would be a good idea for upstream, but I can also see
> why it's a near certainty downstream Linux distros (including Fedora)
> would take it out again in at least some situations to better meet the
Does Fedora also take out setuptools? If not, why not?
> needs
On 7 August 2015 at 03:28, Donald Stufft wrote:
>
>> On Aug 6, 2015, at 5:04 AM, Robert Collins wrote:
>>
>> Yes: but the logic chain from 'its a bad idea' to 'we don't include
>> wheel but we do include setuptools' is the bit I'm
or 'yes and this
is what needs to happen next'.
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mai
On 26 July 2015 at 07:28, Robert Collins wrote:
> On 21 July 2015 at 19:40, Nick Coghlan wrote:
>
>> All of this is why the chart that I believe should be worrying people
>> is the topmost one on this page:
>> http://bugs.python.org/issue?@template=stats
>>
>>
the box be a good fit. This seems to fly in
the exact opposite direction: we're explicitly making it so that
Python builds on these vendor's platforms will not be the same as you
get by checking out the Python source code.
Ugh.
-Rob
--
Robert Collins
Distinguished Technologist
HP Conve
On 18 December 2015 at 06:13, Carlos Barera wrote:
> Hi,
>
> I'm using install_requires in setup.py to specify a specific package my
> project is dependant on.
> When running python setup.py install, apparently the simple index is used
> as an older package is taken from pypi. While
>
What's hap
list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/robertc%40robertcollins.net
>
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
(all?) relevant dimensions.
http://xorshift.di.unimi.it/
I'm favorable to the PCG family these days, though xorshift* and Random123 are
reasonable alternatives.
http://www.pcg-random.org/
https://www.deshawresearch.com/resources_random123.html
--
Robert Kern
"I have come to b
in
PCG and Random123 too ;-)
Quite so!
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma
that is made terrible by our own mad attempt to interpret it as though it had
an underlying truth."
-- Umberto Eco
eypatching functools.wraps, which would tend to be subject to
import ordering races and general ick. I'll likely prep such a
monkeypatch for folk that are stuck on older versions of 2.7 anyhow...
so its not a huge win...
-Rob
--
Robert Collins
Distinguished Technologist
HP
Sadly that has the ordering bug of assigning __wrapped__ first and appears
a little unmaintained based on the bug tracker :(
On 5 Apr 2016 8:10 PM, "Victor Stinner" wrote:
> See https://pypi.python.org/pypi/functools32 for the functools backport
> for Python 2.7.
>
> Victor
>
thetype.append((obj, type))
return None
classIwant.query = gettype()
classIwant().query
thetype[0][1]...
but you've already gotten to classIwant there.
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
___
P
On 6 April 2016 at 15:03, Stephen J. Turnbull wrote:
> Robert Collins writes:
>
> > Sadly that has the ordering bug of assigning __wrapped__ first and appears
> > a little unmaintained based on the bug tracker :(
>
> You can fix two problems with one patch, then!
>
-- ./child_script.py --no-verbose --etc
This is a common idiom across many argument processors. parse_known_args() is
not a good solution for this situation even if you mitigate the prefix issue.
Exact matches of --options are still possible.
--
Robert Kern
"I have come to believe that t
l(x, y, Py_EQ) treats identical objects as equal.
http://hg.python.org/cpython/file/79e5bb0d9b8e/Objects/object.c#l716
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma
that is made terrible by our own mad attempt to interpret it as though i
ject o2)
not a pointer to PyObject?
Typo, I'm fairly certain.
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma
that is made terrible by our own mad attempt to interpret it as though it had
an underlying
t was written, and I personally witnessed all of the history myself so I
don't need it repeated back to me.
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma
that is made terrible by our own mad attempt to interpret it as though it had
an u
s or the analysis, and it isn't
really germane to Chris' historical question. I mention it only because I had
just run across this paper last night, so it was fresh in my mind when you
mentioned studies on the subject.
--
Robert Kern
"I have come to believe that the whole world
So we're making pretty heavy use of PyInstanceMethod_New in our python
binding library that we've written for a bunch of in house tools.
If this isn't the best / correct way to go about adding methods to objects,
what should we be using instead?
On Sun, Apr 7, 2019 at 2:17 AM Jeroen Demeyer wrot
Just PyInstanceMethod_New, and by "adding methods to objects" this is
adding C functions to types defined in C.
Only appears to be called at module import / creation time.
On Mon, Apr 8, 2019 at 10:24 AM Jeroen Demeyer wrote:
> On 2019-04-08 17:08, Robert White wrote:
> &
and thus not included. If you resize the window
(i.e., if you maximize it), you must call the function table.fit() from
IDLE shell.
Does anyone know where is this huge difference in performance coming from?
Can anything be done about it?
All the best,
--
Robert Okadar
IT Consultant
Schedule an
d me.
All the best,
--
Robert Okadar
IT Consultant
Schedule an *online meeting <https://calendly.com/aranea-network/60min>* with
me!
Visit *aranea-mreze.hr* <http://aranea-mreze.hr> or call
* +385 91 300 8887*
On Wed, 10 Apr 2019 at 17:36, Steven D'Aprano wrote:
> Hi Robert
Thank you!
If I understand correctly this is just the hg style branch backport
consequence, multiple copies of a change. Should be safe to skip those.
Rob
On Sun, 28 Apr 2019, 07:11 Chris Withers, wrote:
> Hi All,
>
> I'm in the process of bringing the mock backport up to date, but this
> has
Share your own username with Michael or I and we'll add you there.
Rob
On Mon, 29 Apr 2019, 09:55 Chris Withers, wrote:
> On 28/04/2019 22:21, Robert Collins wrote:
> > Thank you!
>
> Thank me when we get there ;-) Currently in Dec 2018 with a won
They were never needed 😁
Removal is fine with me.
On Wed, 1 May 2019, 09:27 Chris Withers, wrote:
> Hi All,
>
> I have a crazy idea of getting unittest.mock up to 100% code coverage.
>
> I noticed at the bottom of all of the test files in testmock/, there's a:
>
> if __name__ == '__main__':
>
This vector exists today for all new stdlib modules: once added, any
existing dependency could include that name to cater it to be imported on
prior python versions.
Rob
On Wed, 22 May 2019, 17:03 Stephen J. Turnbull, <
[email protected]> wrote:
> Christian Heimes writes:
>
>
- Barry Warsaw
> * The argument clinic - Larry Hastings
>
> If you have other items you'd like to discuss please let me know and I can
> add them to the agenda.
I'd like to talk about overhauling - not tweaking, overhauling - the
standard library testing facil
On 4 March 2013 18:54, Guido van Rossum wrote:
> On Sun, Mar 3, 2013 at 9:24 PM, Robert Collins
> wrote:
>> I'd like to talk about overhauling - not tweaking, overhauling - the
>> standard library testing facilities.
>
> That seems like too big a topic and too v
iew if that would be useful.
-Rob
--
Robert Collins
Distinguished Technologist
HP Cloud Services
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/pyth
On 5 March 2013 05:34, Brett Cannon wrote:
>
>
>
> On Mon, Mar 4, 2013 at 11:29 AM, Barry Warsaw wrote:
>>
>> On Mar 04, 2013, at 07:26 PM, Robert Collins wrote:
>>
>> >It is of course possible for subunit and related tools to run their
>> >own im
tr init; testr run'. Thats
the defined entry point for testr, and .testr.conf can specify running
make, or setup.py build or whatever else is needed to run tests.
I would love to see a declaritive interface so that you can tell that
is what you should run.
stribute packages they want to be sure
they work. Running the tests is a pretty good signal for that, but
having every package slightly different adds to the work they need to
do. Being able to do 'setup.py test' consistently, everywhere - that
would be great.
-Rob
--
Robert Collins
Di
On 5 March 2013 12:49, Eli Bendersky wrote:
>
> On Mon, Mar 4, 2013 at 2:14 PM, Barry Warsaw wrote:
>>
>> On Mar 05, 2013, at 11:01 AM, Robert Collins wrote:
>>
>> >The big thing is automated tools, not developers.
>>
>> Exactly.
>
> I don'
ther see how we can
> make the TestResult play *better* with those requirements. That discussion
> probably belongs in another thread - or at
> the summit.
Right - all I wanted was to flag that you and I and any other
interested parties should discuss this at the summit :).
-Rob
hat was
> discussed, and my email was in this context.
So that is interesting, but its not sufficient to meet the automation
need Barry is calling out, unless all test suites can be run by
'python -m unittest discover' with no additional parameters [and a
pretty large subset cannot].
e core use cases and differences to what
TestResult is in pretty short order. We can spider out from there as
folk desire.
-Rob
--
Robert Collins
Distinguished Technologist
HP Cloud Services
___
Python-Dev mailing list
[email protected]
http://mai
On 5 March 2013 20:02, Lennart Regebro wrote:
> On Tue, Mar 5, 2013 at 1:41 AM, Robert Collins
> wrote:
>> So that is interesting, but its not sufficient to meet the automation
>> need Barry is calling out, unless all test suites can be run by
>> 'python -m unittest
mean that they have given you permission
to redistribute it. If the agreements that you have with the copyright owner do
not mention redistribution, you do not have permission to redistribute it.
IANAL, TINLA.
--
Robert Kern
"I have come to believe that the whole world is an enigma, a har
projects would be making use of this
ability already -- just think of uses for numpy's subclasses of "float".
We don't.
[~]
|1> type(float(np.float64(1.0)))
float
[~]
|2> type(int(np.int32(1)))
int
--
Robert Kern
"I have come to believe that the whole world is an
e physical disc?
CDROMs - Joliet IIRC - so yes, physical disc.
-Rob
--
Robert Collins
Distinguished Technologist
HP Cloud Services
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.py
predictable. I have never seen
__subclasses__ actually used in production code, so I'm wondering
whether someone might be affected by such a change.
I do use a package that does use __subclasses__ in production code, but the
order is unimportant.
--
Robert Kern
"I have come to believ
4, 0), dtype=float64)
[~]
|5> np.empty([3,4,0])[1]
array([], shape=(4, 0), dtype=float64)
[~]
|6> len(np.empty([3,4,0]))
3
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma
that is made terrible by our own mad attempt to interpret
(rarer still is testing for emptiness not knowing if it is an array or some
other sequence). What people usually want from bool(some_array) is either
some_array.all() or some_array.any(). In the face of this ambiguity, numpy
refuses the temptation to guess and raises an exception explaining matt
On 2013-06-14 23:31, Robert Kern wrote:
On 2013-06-14 21:55, R. David Murray wrote:
On Fri, 14 Jun 2013 21:12:00 +0200, Martin Schultz wrote:
2. Testing for empty lists or empty ndarrays:
In principle, `len(x) == 0` will do the trick. **BUT** there are several
caveats here:
- `len
On 11 June 2016 at 04:09, Victor Stinner wrote:
..> We should design a CLI command to do timeit+compare at once.
http://judge.readthedocs.io/en/latest/ might offer some inspiration
There's also ministat -
https://www.freebsd.org/cgi/man.cgi?query=ministat&apropos=0&sektion=0&manpath=FreeBSD+8-cu
On 16 Jun 2016 6:55 PM, "Larry Hastings" wrote:
>
>
> Why do you call it only "semi-fixed"? As far as I understand it, the
semantics of os.urandom() in 3.5.2rc1 are indistinguishable from reading
from /dev/urandom directly, except it may not need to use a file handle.
Which is a contract change
On 14 December 2016 at 01:26, Sesha Narayanan Subbiah
wrote:
> Hello
>
>
> I have some implementation that currently uses python 2.6.4, which I m
> trying to upgrade to Python 2.7.6. After upgrade, I get the following error:
>
>
> "expected string or Unicode object, memoryview found"
>
>
> On chec
On 14 December 2016 at 18:10, Sesha Narayanan Subbiah
wrote:
> Hi Rob
>
> Thanks for your reply.
>
> From http://legacy.python.org/download/, I could see that the current
> production releases are Python 3.4 and Python 2.7.6.
Nope - https://www.python.org/downloads/ - 2.7.12 and 3.5.2 are
current
On 17 December 2016 at 08:24, Guido van Rossum wrote:
> I am beginning to think that `from __future__ import unicode_literals` does
> more harm than good. I don't recall exactly why we introduced it, but with
> the restoration of u"" literals in Python 3.3 we have a much better story
> for writing
On 24 March 2017 at 04:59, INADA Naoki wrote:
> And this issue is relating to it too: http://bugs.python.org/issue29716
>
> In short, "namespace package" is for make it possible to `pip install
> foo_bar foo_baz`,
> when foo_bar provides `foo.bar` and foo_baz provides `foo.baz`
> package. (foo is
nobody is payed for reviewing submissions, but maybe it just
got overlooked?
You can find the pull request at [2].
Thanks in advance for any feedback.
Best regards
Robert
[1] https://docs.python.org/devguide/pullrequest.html#reviewing
[2] https://github.com/python/cpython/pull/1698
1 - 100 of 315 matches
Mail list logo
