wiredfool
95a25a0d82
input parameter filtering
2016-02-04 07:19:54 -08:00
wiredfool
8d518a3f4d
3.2.0-dev versioning
2016-01-04 03:03:26 -08:00
wiredfool
fff5536b37
3.1.0 version
2016-01-04 02:04:23 -08:00
wiredfool
0f9f5cd8db
3.1.0-rc1 versioning
2016-01-01 16:00:32 +00:00
Andrew Murray
8f9b3a7372
Changed arcs, chords and pie slices to use floats
2015-12-09 00:28:52 +11:00
hugovk
7f83226e36
Remove old, closed-source PIL Plus extensions
2015-10-16 19:48:01 +03:00
Andrew Murray
6bd7e7f02d
Removed trailing whitespace
2015-10-11 21:24:35 +11:00
Alex Clark
1f72110040
PEP440 [ci skip]
2015-10-05 05:39:08 -04:00
wiredfool
58fedea740
3.1 Dev versioning
2015-10-01 21:39:00 +01:00
wiredfool
0177cceac4
3.0 Release versioning
2015-10-01 21:39:00 +01:00
wiredfool
4cd29c10d3
Fix indentation to match actual code flow
2015-09-15 01:01:04 -07:00
Andrew Murray
2d9f091a30
Improved handling of getink color
2015-08-22 22:29:23 +10:00
Andrew Murray
f6d11a2803
Only use fast rotate operations if the expand flag is in use or the image is square
2015-08-06 00:23:14 +10:00
Alex Clark
93eb15bec7
Commence 3.0.0.dev0
2015-07-02 05:20:15 -04:00
Alex Clark
80672b61e8
This is 2.9.0
...
Fixes #1174
2015-07-01 14:33:56 -04:00
Alex Clark
445a8c06fc
Bump
2015-06-30 08:04:35 -04:00
Alex Clark
96944e2dd6
Bump
2015-06-29 08:57:55 -04:00
Benoit Pierre
4f6c366e75
fix imaging leaks in putdata and getlist
2015-04-16 20:09:39 +02:00
Alex Clark
5cfc34b287
Begin 2.9.0 development with 2.9.0.dev0
...
Use PEP440 syntax to identify development branch and keep pyroma happy: https://www.python.org/dev/peps/pep-0440/#developmental-releases .
2015-04-02 14:53:49 -04:00
Alex Clark
3f09b8f171
Prep 2.8.1
2015-04-02 10:59:03 -04:00
Alex Clark
860a1dedf1
Prep 2.8.0
...
No ci skip here because let's see CI run w/new version numbers. I'm starting to think (again) this bump should happen immediately after the release instead of right before the next? But I know @wiredfool had some objection to this at some point. As a compromise, maybe we could change to 2.9.0dev immediately following the release of 2.8.0.
2015-03-27 07:02:02 -04:00
wiredfool
0f05eb287a
Version Bump --2.7.0
2014-12-31 20:42:57 -08:00
wiredfool
e16ee15f2c
Merge pull request #997 from homm/replace-resize
...
Replace resize method
2014-11-27 10:26:48 -08:00
wiredfool
8a3302ba5d
Merge pull request #961 from homm/fast-box-blur
...
Merge Fast Gaussian Blur
2014-11-27 10:20:11 -08:00
homm
bc0f896a47
rename Antialias and stretch to resample
2014-11-19 14:36:00 +03:00
homm
1a097d2e02
Merge commit 'e0b94d65bedb4a2124228aa579686a3ba2974d11' into replace-resize
2014-11-19 13:45:04 +03:00
homm
814dd3123e
fix comments
2014-11-19 13:15:50 +03:00
homm
41029f0149
make im.stretch strong alias to im.resize.
...
mark im.stretch as deprecated.
2014-11-19 03:26:17 +03:00
wiredfool
f75c5562c7
Fix #1008 , Correct argument to PySequence_Fast_GET_ITEM
2014-11-13 15:33:37 -08:00
homm
aba798af25
replace resize implementation
2014-11-09 21:52:16 +03:00
homm
c22af89ef0
optimize memory usage
2014-11-09 03:05:56 +03:00
homm
c8471bcbda
Hide stretch implementation detail in Antialias.c
2014-11-09 03:05:56 +03:00
homm
32079b1dcc
make transpose part of public api
2014-11-07 03:37:12 +03:00
homm
36a35e7e27
update box_blur help
...
fix code style for `!`
fix spelling
2014-10-30 14:19:12 +03:00
homm
274f0a14ba
change arguments order and names to match other functions
2014-10-25 17:16:14 +04:00
homm
65173f946b
replace gaussian blur with extended box blur implementation
2014-10-25 16:36:41 +04:00
homm
d89c9ab750
Merge branch 'gaussian-refactor' into fast-box-blur
2014-10-25 15:50:57 +04:00
homm
d7d92275f1
Change arguments order and names
2014-10-25 04:28:05 +04:00
homm
516bd90cf7
support for multiple passes with only two transposes
2014-10-19 13:54:13 +04:00
homm
23068e49be
allow float radius (without implementation)
2014-10-12 19:24:38 +04:00
homm
d49459f5b2
box blur dummy
2014-10-12 16:30:00 +04:00
homm
84b9f16bfd
add effective_scale to all APIs
2014-10-12 03:29:20 +04:00
wiredfool
9634e437ef
Version Bump -- 2.6.0
2014-10-01 09:59:00 -07:00
wiredfool
6abc0d2f40
Version Bump - 2.6.0-rc1
2014-09-29 13:14:49 -07:00
wiredfool
2d634d3019
Bump Version/Changelog
2014-08-19 08:52:29 -07:00
wiredfool
c9c80f9da5
Use PySequence_Fast for Image.putdata
...
Pre-Commit:
$ NOSE_PROCESSES=0 time ./test-installed.py Tests/test_image_putdata.py
...
----------------------------------------------------------------------
Ran 3 tests in 131.623s
OK
131.77user 0.18system 2:14.04elapsed 98%CPU (0avgtext+0avgdata 325632maxresident)k
87376inputs+8outputs (314major+47333minor)pagefaults 0swaps
Post:
$ NOSE_PROCESSES=0 time ./test-installed.py Tests/test_image_putdata.py
...
----------------------------------------------------------------------
Ran 3 tests in 0.534s
OK
0.77user 0.05system 0:00.83elapsed 99%CPU (0avgtext+0avgdata 296352maxresident)k
0inputs+0outputs (0major+21462minor)pagefaults 0swaps
2014-07-23 15:39:24 -07:00
wiredfool
5def1010c7
DRY, moved case inside loop
2014-07-23 15:16:23 -07:00
wiredfool
a5aea42bc9
Use PySequence_Fast* to iterate over the list
...
Pre commit:
$ NOSE_PROCESSES=0 PILLOW_RUN_KNOWN_BAD=1 time ./test-installed.py Tests/test_image_point.py
..
----------------------------------------------------------------------
Ran 2 tests in 132.056s
OK
131.63user 0.62system 2:12.28elapsed 99%CPU (0avgtext+0avgdata 292176maxresident)k
264inputs+0outputs (2major+451088minor)pagefaults 0swaps
Post:
$ NOSE_PROCESSES=0 PILLOW_RUN_KNOWN_BAD=1 time ./test-installed.py Tests/test_image_point.py
..
----------------------------------------------------------------------
Ran 2 tests in 0.338s
OK
0.52user 0.06system 0:00.59elapsed 98%CPU (0avgtext+0avgdata 257584maxresident)k
176inputs+32outputs (2major+18033minor)pagefaults 0swaps
$ python --version
Python 2.7.6 (2.3.1+dfsg-1~ppa1, Jun 20 2014, 09:27:47)
[PyPy 2.3.1 with GCC 4.6.3]
2014-07-23 14:46:37 -07:00
Alex Clark
4b40839970
Revert "Bump"
...
This reverts commit 4fe5d520fb
.
Hah, foiled by PEP8
2014-07-15 06:15:31 -04:00
Alex Clark
4fe5d520fb
Bump
...
Though I hate the 'dev' designation I want something to indicate master is where development for the next major version happens. I think we've previously disagreed on simply 'X.X.X' so I'm going with 'X.X.Xdev' to see if that is more palatable. :-)
2014-07-15 06:02:34 -04:00