| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Faster check for empty range in str() | Daniele Varrazzo | 2018-10-04 | 1 | -1/+1 |
| | | |||||
| * | Implement __str__ for range types | Michel Albert | 2018-09-30 | 1 | -0/+13 |
| | | |||||
| * | Drop 2to3 build step; make all code compatible with all Pythons | Jon Dufresne | 2017-12-11 | 1 | -3/+8 |
| | | | | | | | | | | | | | | | | | Make all library code compatible with both Python 2 and Python 3. Helps move to modern Python idioms. Can now write for Python 3 (with workarounds for Python 2) instead of the other way around. In the future, when it is eventually time to drop Python 2, the library will be in a better position to remove workarounds Added a very small comparability module compat.py where required. It includes definitions for: - text_type -- A type. str on Python 3. unicode on Python 2. - string_types -- A tuple. Contains only str on Python 3. Contains str & unicode on Python 2. | ||||
| * | Use dict comprehensions | Daniele Varrazzo | 2017-11-28 | 1 | -5/+2 |
| | | |||||
| * | Python source cleanup using flake8 | Daniele Varrazzo | 2016-10-11 | 1 | -14/+25 |
| | | |||||
| * | Dropped use of b() "macro" and 2to3 fixer | Daniele Varrazzo | 2016-08-15 | 1 | -7/+7 |
| | | | | | Just use the b"" strings syntax supported from python 2.6. | ||||
| * | Make Range pickleable | Jonathan Ross Rogers | 2016-08-07 | 1 | -0/+11 |
| | | |||||
| * | Merge branch 'range_sort' | Daniele Varrazzo | 2014-02-22 | 1 | -4/+35 |
| |\ | |||||
| | * | Hardcode the list of attributes to be used in comparison | Daniele Varrazzo | 2014-02-22 | 1 | -1/+1 |
| | | | | | | | | | Comparing Range subclasses may lead to surprises. | ||||
| | * | Added implementation for Range gt and ge operators | Daniele Varrazzo | 2014-02-22 | 1 | -13/+15 |
| | | | | | | | | | | | Using a common implementation for all the operators. Note that lt is the one used by sort so it's nice it's the fastest. | ||||
| | * | New implementation of Range sorting that works for Python 2.5 to 3.3, at least. | Chris Withers | 2014-02-18 | 1 | -6/+26 |
| | | | |||||
| | * | Provide a stable and consistent sort order for Range objects. | Chris Withers | 2014-02-12 | 1 | -4/+13 |
| | | | | | | | | | This matches postgres server-side behaviour and helps client applications that need to sort based on the primary key of tables where the primary key is or contains a range. | ||||
| * | | Fixed error message on range parsing failed | Daniele Varrazzo | 2014-02-22 | 1 | -1/+1 |
| |/ | |||||
| * | cater for comparison of subclasses | Chris Withers | 2013-05-26 | 1 | -1/+1 |
| | | |||||
| * | raising an exception here rather than returning False causes problems with ↵ | Chris Withers | 2013-05-26 | 1 | -1/+1 |
| | | | | | SQLAlchemy's internal state tracking | ||||
| * | more useful error message when comparing ranges with non-ranges | Chris Withers | 2013-05-26 | 1 | -0/+2 |
| | | |||||
| * | Make sure to return a bytes string from numeric range adapter | Daniele Varrazzo | 2013-04-21 | 1 | -3/+3 |
| | | |||||
| * | A couple of typos fixed | Daniele Varrazzo | 2013-04-07 | 1 | -1/+1 |
| | | |||||
| * | Fixed range adaptation on Python 3 | Daniele Varrazzo | 2013-03-16 | 1 | -10/+10 |
| | | |||||
| * | More helpful error messasge on Range order attempts | Daniele Varrazzo | 2012-09-25 | 1 | -1/+3 |
| | | |||||
| * | Added documentation for range types and adaptation | Daniele Varrazzo | 2012-09-24 | 1 | -35/+44 |
| | | |||||
| * | Don't need to implement __new__ to make an immutable class | Daniele Varrazzo | 2012-09-24 | 1 | -4/+1 |
| | | |||||
| * | Fixed search of types into schemas. | Daniele Varrazzo | 2012-09-24 | 1 | -3/+3 |
| | | | | | | | We don't need to look for stuff implicitly into pg_catalog as all the builtin ranges are already registered. So just search into 'public' if the schema is not specified. | ||||
| * | Range objects cannot be ordered | Daniele Varrazzo | 2012-09-23 | 1 | -0/+5 |
| | | |||||
| * | Range objects are nonzero when not empty | Daniele Varrazzo | 2012-09-23 | 1 | -0/+3 |
| | | |||||
| * | Range objects are immutable and hashable | Daniele Varrazzo | 2012-09-23 | 1 | -1/+14 |
| | | |||||
| * | Dropped Range._empty attribute | Daniele Varrazzo | 2012-09-23 | 1 | -13/+13 |
| | | | | | | We can do with just _bounds: it will make eq and hash easier to implement in a consistent way | ||||
| * | Added in operator for ranges | Daniele Varrazzo | 2012-09-23 | 1 | -0/+16 |
| | | |||||
| * | NumberRange renamed to NumericRange | Daniele Varrazzo | 2012-09-23 | 1 | -7/+7 |
| | | | | | | | I was avoiding Numeric to avoid conflicting with the 'numeric' Postgres type, which is an alias for 'decimal'. But now that there is a single numeric range I can use the preferred name | ||||
| * | Dropped Range classes for specific numeric types | Daniele Varrazzo | 2012-09-23 | 1 | -15/+3 |
| | | |||||
| * | Added first implementation of Range type, adapter, typecaster | Daniele Varrazzo | 2012-09-23 | 1 | -0/+435 |
 |
index : delta/python-packages/psycopg2.git | |
| github.com: psycopg/psycopg2.git |
| summaryrefslogtreecommitdiff |