Message217297
| Author | neologix |
|---|---|
| Recipients | josh.r, jtaylor, neologix, njs, pitrou, skrah, vstinner |
| Date | 2014-04-27.17:48:44 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <CAH_1eM0rr1VxsuJSoV+GcvMtcUp3y4WYH2OAzQMo=LcV+Kw6Tg@mail.gmail.com> |
| In-reply-to | <1398620509.5.0.0569535389024.issue21233@psf.upfronthosting.co.za> |
| Content | |
|---|---|
> And your test.py produces the same result. Are you sure you don't have a ulimit set on address space?
Yep, I'm sure:
$ ulimit -v
unlimited
It's probably due to the exponential over-allocation used by the array
(to guarantee amortized constant cost).
How about:
python -c "b = bytes('x' * <large>)" |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-04-27 17:48:44 | neologix | set | recipients: + neologix, pitrou, vstinner, njs, skrah, jtaylor, josh.r |
| 2014-04-27 17:48:44 | neologix | link | issue21233 messages |
| 2014-04-27 17:48:44 | neologix | create | |