Thread: [Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets (Page 17)

Brought to you by: zzzeek

sqlalchemy-commits

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-04-08 21:24:30

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/ffec6ab936a7/
Changeset:   ffec6ab936a7
Branch:      None
User:        zzzeek
Date:        2015-04-08 21:23:26+00:00
Summary:     - add test support for MySQLdb with use_unicode=1 or using mysqlclient on py3k

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/fbd85c0958ab/
Changeset:   fbd85c0958ab
Branch:      rel_0_9
User:        zzzeek
Date:        2015-04-08 21:24:16+00:00
Summary:     - add test support for MySQLdb with use_unicode=1 or using mysqlclient on py3k

(cherry picked from commit ffec6ab936a73f5cbe63d9409beb12f1f0307d0b)

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-04-10 15:20:54

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/55c26710a1f6/
Changeset:   55c26710a1f6
Branch:      None
User:        zzzeek
Date:        2015-04-10 15:20:14+00:00
Summary:     - Fixed issue where a :class:`.MetaData` object that used a naming
convention would not properly work with pickle.  The attribute was
skipped leading to inconsistencies and failures if the unpickled
:class:`.MetaData` object were used to base additional tables
from.
fixes #3362

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/e7cf56828486/
Changeset:   e7cf56828486
Branch:      rel_0_9
User:        zzzeek
Date:        2015-04-10 15:20:39+00:00
Summary:     - Fixed issue where a :class:`.MetaData` object that used a naming
convention would not properly work with pickle.  The attribute was
skipped leading to inconsistencies and failures if the unpickled
:class:`.MetaData` object were used to base additional tables
from.
fixes #3362

(cherry picked from commit 55c26710a1f6d6c6f87a9752035bc160f93b38d0)

Affected #:  3 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-04-12 17:00:00

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/fc702c9d8098/
Changeset:   fc702c9d8098
Branch:      None
User:        zzzeek
Date:        2015-04-12 16:59:31+00:00
Summary:     - adjust for "0"

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/2f1a17de621a/
Changeset:   2f1a17de621a
Branch:      rel_0_9
User:        zzzeek
Date:        2015-04-12 16:59:46+00:00
Summary:     - adjust for "0"

(cherry picked from commit fc702c9d809878c5a5d85876bfa23e17177940c2)

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-04-21 14:05:08

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/c2e300250324/
Changeset:   c2e300250324
Branch:      None
User:        zzzeek
Date:        2015-04-21 14:04:02+00:00
Summary:     - Added the string value ``"none"`` to those accepted by the
:paramref:`.Pool.reset_on_return` parameter as a synonym for ``None``,
so that string values can be used for all settings, allowing
.ini file utilities like :func:`.engine_from_config` to be usable
without issue.
fixes #3375

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/384c885ed078/
Changeset:   384c885ed078
Branch:      rel_0_9
User:        zzzeek
Date:        2015-04-21 14:04:48+00:00
Summary:     - Added the string value ``"none"`` to those accepted by the
:paramref:`.Pool.reset_on_return` parameter as a synonym for ``None``,
so that string values can be used for all settings, allowing
.ini file utilities like :func:`.engine_from_config` to be usable
without issue.
fixes #3375

(cherry picked from commit c2e3002503242331fc8f2b314e0d4f3c65de9d73)

Affected #:  3 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-04-21 15:04:59

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/732fb99fc0af/
Changeset:   732fb99fc0af
Branch:      None
User:        zzzeek
Date:        2015-04-21 15:04:21+00:00
Summary:     - add a warning to SingletonThreadPool that it isn't for general use

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/f03a086e8529/
Changeset:   f03a086e8529
Branch:      rel_0_9
User:        zzzeek
Date:        2015-04-21 15:04:43+00:00
Summary:     - add a warning to SingletonThreadPool that it isn't for general use

(cherry picked from commit 732fb99fc0afbeb69d684b2bfa6d0be6250919a3)

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-04-22 23:36:29

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/fa88d0e8ffbe/
Changeset:   fa88d0e8ffbe
Branch:      None
User:        zzzeek
Date:        2015-04-22 22:56:05+00:00
Summary:     - ensure that info isn't blown away after the do_connect event

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/b957cdbd945f/
Changeset:   b957cdbd945f
Branch:      ticket_3355
User:        zzzeek
Date:        2015-04-22 23:35:16+00:00
Summary:     - fixes for some tests, staticpool

Affected #:  3 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-04-23 18:27:02

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/350d002ee9f6/
Changeset:   350d002ee9f6
Branch:      None
User:        zzzeek
Date:        2015-04-23 18:21:56+00:00
Summary:     - update date
- repair category for EXISTS issue

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/0fc751e4abea/
Changeset:   0fc751e4abea
Branch:      None
User:        zzzeek
Date:        2015-04-23 18:21:56+00:00
Summary:     1.0.1

Affected #:  2 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-04-24 17:49:39

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/30e4d9b3ff1d/
Changeset:   30e4d9b3ff1d
Branch:      ticket_3355
User:        zzzeek
Date:        2015-04-23 20:30:12+00:00
Summary:     Merge branch 'master' into ticket_3355

Affected #:  31 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/e73f73538237/
Changeset:   e73f73538237
Branch:      None
User:        zzzeek
Date:        2015-04-24 17:49:09+00:00
Summary:     - Fixed regression regarding the declarative ``__declare_first__``
and ``__declare_last__`` accessors where these would no longer be
called on the superclass of the declarative base.
fixes #3383

Affected #:  7 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-04-24 19:54:20

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/e77cf339ee50/
Changeset:   e77cf339ee50
Branch:      None
User:        Gaëtan de Menten
Date:        2015-04-24 12:26:42+00:00
Summary:     micro-optimize unique_list

This makes unique_list approx 2x faster in my (simple) tests
Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/f7e89f887fa4/
Changeset:   f7e89f887fa4
Branch:      None
User:        zzzeek
Date:        2015-04-24 19:52:42+00:00
Summary:     Merge remote-tracking branch 'origin/pr/169'

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-04-27 19:23:46

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/e25ef01fbb70/
Changeset:   e25ef01fbb70
Branch:      None
User:        zzzeek
Date:        2015-04-27 19:05:41+00:00
Summary:     - Fixed regression due to :ticket:`3282` where the ``tables`` collection
passed as a keyword argument to the :meth:`.DDLEvents.before_create`,
:meth:`.DDLEvents.after_create`, :meth:`.DDLEvents.before_drop`, and
:meth:`.DDLEvents.after_drop` events would no longer be a list
of tables, but instead a list of tuples which contained a second
entry with foreign keys to be added or dropped.  As the ``tables``
collection, while documented as not necessarily stable, has come
to be relied upon, this change is considered a regression.
Additionally, in some cases for "drop", this collection would
be an iterator that would cause the operation to fail if
prematurely iterated.   The collection is now a list of table
objects in all cases and test coverage for the format of this
collection is now added.
fixes #3391

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/e5c20fce9354/
Changeset:   e5c20fce9354
Branch:      None
User:        zzzeek
Date:        2015-04-27 19:21:18+00:00
Summary:     - replace old crufty ddl event test fixture with mock

Affected #:  2 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-04-29 04:06:30

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/93b5eae9843d/
Changeset:   93b5eae9843d
Branch:      None
User:        zzzeek
Date:        2015-04-29 04:05:25+00:00
Summary:     - add boldface for "viable" plus a note describing that this
refers to the table having a primary key.  fixes #3398

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/933af1078f93/
Changeset:   933af1078f93
Branch:      rel_0_9
User:        zzzeek
Date:        2015-04-29 04:06:12+00:00
Summary:     - add boldface for "viable" plus a note describing that this
refers to the table having a primary key.  fixes #3398

(cherry picked from commit 93b5eae9843d423378f68be928a4f1e6fcacfb87)

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-04-30 16:55:32

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/20e3df602846/
Changeset:   20e3df602846
Branch:      None
User:        zzzeek
Date:        2015-04-30 16:53:27+00:00
Summary:     - Fixed regression from as yet unreleased 0.9.10 where the new addition
of ``entity`` to the :attr:`.Query.column_descriptions` accessor
would fail if the target entity was produced from a core selectable
such as a :class:`.Table` or :class:`.CTE` object.
fixes #3403  references #3320

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/de8a9fd81408/
Changeset:   de8a9fd81408
Branch:      rel_0_9
User:        zzzeek
Date:        2015-04-30 16:55:07+00:00
Summary:     - Fixed regression from as yet unreleased 0.9.10 where the new addition
of ``entity`` to the :attr:`.Query.column_descriptions` accessor
would fail if the target entity was produced from a core selectable
such as a :class:`.Table` or :class:`.CTE` object.
fixes #3403  references #3320

(cherry picked from commit 20e3df602846bb1d8940b5138f21ef203c99bade)

Affected #:  3 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-05-01 01:31:21

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/681276b5b4ae/
Changeset:   681276b5b4ae
Branch:      None
User:        zzzeek
Date:        2015-05-01 01:26:48+00:00
Summary:     - Fixed regression from 0.9.10 prior to release due to :ticket:`3349`
where the check for query state on :meth:`.Query.update` or
:meth:`.Query.delete` compared the empty tuple to itself using ``is``,
which fails on Pypy to produce ``True`` in this case; this would
erronously emit a warning in 0.9 and raise an exception in 1.0.
fixes #3405

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/7f658511954d/
Changeset:   7f658511954d
Branch:      rel_0_9
User:        zzzeek
Date:        2015-05-01 01:30:57+00:00
Summary:     - Fixed regression from 0.9.10 prior to release due to :ticket:`3349`
where the check for query state on :meth:`.Query.update` or
:meth:`.Query.delete` compared the empty tuple to itself using ``is``,
which fails on Pypy to produce ``True`` in this case; this would
erronously emit a warning in 0.9 and raise an exception in 1.0.
fixes #3405

(cherry picked from commit 681276b5b4ae48924c85a1c26af3f9bde3d77b5f)

Affected #:  2 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-05-01 13:21:25

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/24d6ea362e75/
Changeset:   24d6ea362e75
Branch:      None
User:        zzzeek
Date:        2015-05-01 13:20:10+00:00
Summary:     - Repaired / added to tests yet more expressions that were reported
as failing with the new 'entity' key value added to
:attr:`.Query.column_descriptions`, the logic to discover the "from"
clause is again reworked to accommodate columns from aliased classes,
as well as to report the correct value for the "aliased" flag in these
cases.
fixes #3409

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/aee58e21631c/
Changeset:   aee58e21631c
Branch:      rel_0_9
User:        zzzeek
Date:        2015-05-01 13:21:05+00:00
Summary:     - Repaired / added to tests yet more expressions that were reported
as failing with the new 'entity' key value added to
:attr:`.Query.column_descriptions`, the logic to discover the "from"
clause is again reworked to accommodate columns from aliased classes,
as well as to report the correct value for the "aliased" flag in these
cases.
fixes #3409

(cherry picked from commit 24d6ea362e757c79b3bada663cf6fc9f262dae4f)

Affected #:  2 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-05-01 13:42:12

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/088666e8f3de/
Changeset:   088666e8f3de
Branch:      None
User:        zzzeek
Date:        2015-05-01 13:38:21+00:00
Summary:     - Fixed an import that prevented "pypy setup.py test" from working
correctly.
fixes #3406

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/f1da4ce03d7f/
Changeset:   f1da4ce03d7f
Branch:      rel_0_9
User:        zzzeek
Date:        2015-05-01 13:38:45+00:00
Summary:     - Fixed an import that prevented "pypy setup.py test" from working
correctly.
fixes #3406

Affected #:  2 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-05-01 16:37:20

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/95949db715ff/
Changeset:   95949db715ff
Branch:      None
User:        zzzeek
Date:        2015-05-01 16:33:45+00:00
Summary:     - Repair _reinstall_default_lookups to also flip the _extended flag
off again so that test fixtures setup/teardown instrumentation as
expected
- clean up test_extendedattr.py and fix it to no longer leak
itself outside by ensuring _reinstall_default_lookups is always called,
part of #3408
- Fixed bug where when using extended attribute instrumentation system,
the correct exception would not be raised when :func:`.class_mapper`
were called with an invalid input that also happened to not
be weak referencable, such as an integer.
fixes #3408

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/c613ec128ffe/
Changeset:   c613ec128ffe
Branch:      rel_0_9
User:        zzzeek
Date:        2015-05-01 16:36:58+00:00
Summary:     - Repair _reinstall_default_lookups to also flip the _extended flag
off again so that test fixtures setup/teardown instrumentation as
expected
- clean up test_extendedattr.py and fix it to no longer leak
itself outside by ensuring _reinstall_default_lookups is always called,
part of #3408
- Fixed bug where when using extended attribute instrumentation system,
the correct exception would not be raised when :func:`.class_mapper`
were called with an invalid input that also happened to not
be weak referencable, such as an integer.
fixes #3408

(cherry picked from commit 95949db715ff54be01bfd260a51903ede60597ae)

Affected #:  3 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-05-02 14:27:42

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/b2196dd953e6/
Changeset:   b2196dd953e6
Branch:      None
User:        zzzeek
Date:        2015-05-02 14:08:11+00:00
Summary:     - start qualifying some regressions as "unexpected use"
regressions; regressions where we didn't know an API even worked
in a particular way or that anyone were using it in such a way
hence had no tests for such case.

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/77db0ef6ac03/
Changeset:   77db0ef6ac03
Branch:      None
User:        zzzeek
Date:        2015-05-02 14:27:03+00:00
Summary:     - Fixed bug in enhanced constraint-attachment logic introduced in
:ticket:`3341` where in the unusual case of a constraint that refers
to a mixture of :class:`.Column` objects and string column names
at the same time, the auto-attach-on-column-attach logic will be
skipped; for the constraint to be auto-attached in this case,
all columns must be assembled on the target table up front.
Added a new section to the migration document regarding the
original feature as well as this change.
fixes #3411

Affected #:  4 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-05-05 20:55:50

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/be81cb200d9e/
Changeset:   be81cb200d9e
Branch:      None
User:        zzzeek
Date:        2015-05-05 20:55:09+00:00
Summary:     - fix typo MANYTOONE -> MANYTOMANY, fixes #3415

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/eb59cb175375/
Changeset:   eb59cb175375
Branch:      rel_0_9
User:        zzzeek
Date:        2015-05-05 20:55:33+00:00
Summary:     - fix typo MANYTOONE -> MANYTOMANY, fixes #3415

(cherry picked from commit be81cb200d9efb45c3bf331315c54dff778b5de6)

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-05-07 16:35:38

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/ae4c2b6cbee0/
Changeset:   ae4c2b6cbee0
Branch:      None
User:        zzzeek
Date:        2015-05-07 16:34:38+00:00
Summary:     - bump zs version due to not yet diagnosed error

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/644b75c8a6de/
Changeset:   644b75c8a6de
Branch:      rel_0_9
User:        zzzeek
Date:        2015-05-07 16:34:59+00:00
Summary:     - bump zs version due to not yet diagnosed error

(cherry picked from commit ae4c2b6cbee0f993b3937237411df7fb8e66592d)

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-05-07 17:48:20

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/4f31db82100b/
Changeset:   4f31db82100b
Branch:      None
User:        zzzeek
Date:        2015-05-07 17:47:38+00:00
Summary:     - re-tag zzzeeksphinx w/ new version supporting sphinx 1.3

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/25664b06f9fd/
Changeset:   25664b06f9fd
Branch:      rel_0_9
User:        zzzeek
Date:        2015-05-07 17:48:01+00:00
Summary:     - re-tag zzzeeksphinx w/ new version supporting sphinx 1.3

(cherry picked from commit 4f31db82100bee20284d8e9273ac9c6d147a32e3)

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-05-07 20:06:32

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/6b55842eef3a/
Changeset:   6b55842eef3a
Branch:      rel_0_9
User:        zzzeek
Date:        2015-05-07 20:05:48+00:00
Summary:     RTD doesn't seem to want to refresh on a git tag so go back to using
release numbers

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/ed73a95db6b5/
Changeset:   ed73a95db6b5
Branch:      None
User:        zzzeek
Date:        2015-05-07 20:06:11+00:00
Summary:     RTD doesn't seem to want to refresh on a git tag so go back to using
release numbers

(cherry picked from commit 6b55842eef3a243d275bdd5630c1fe62d98e8371)

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-05-07 20:19:45

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/6d7901fa7d3f/
Changeset:   6d7901fa7d3f
Branch:      None
User:        zzzeek
Date:        2015-05-07 20:19:08+00:00
Summary:     - plead with RTD to please please use the correct version

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/3c7064201226/
Changeset:   3c7064201226
Branch:      rel_0_9
User:        zzzeek
Date:        2015-05-07 20:19:32+00:00
Summary:     - plead with RTD to please please use the correct version

(cherry picked from commit 6d7901fa7d3feb5c7894e31a48d249b445557f20)

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-05-22 17:28:25

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/c581b907b3f1/
Changeset:   c581b907b3f1
Branch:      None
User:        zzzeek
Date:        2015-05-22 17:27:09+00:00
Summary:     - document fully how to use autoincrement w/ SQLite including
non-Integer column types, fixes #2075

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/0771e165063c/
Changeset:   0771e165063c
Branch:      rel_0_9
User:        zzzeek
Date:        2015-05-22 17:27:53+00:00
Summary:     - document fully how to use autoincrement w/ SQLite including
non-Integer column types, fixes #2075

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-05-24 13:50:06

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/1bb9c99ea9f3/
Changeset:   1bb9c99ea9f3
Branch:      None
User:        zzzeek
Date:        2015-05-24 13:49:14+00:00
Summary:     - liberalize list.remove() regexp as recent Pypy versions
format this message differently than cpython

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/c430cdf674e5/
Changeset:   c430cdf674e5
Branch:      rel_0_9
User:        zzzeek
Date:        2015-05-24 13:49:46+00:00
Summary:     - liberalize list.remove() regexp as recent Pypy versions
format this message differently than cpython

(cherry picked from commit 1bb9c99ea9f3e36e5d4a9f1d4f21f1d0a252db4a)

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

From: Bitbucket <com...@bi...> - 2015-05-27 17:54:38

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/1bc7881171e0/
Changeset:   1bc7881171e0
Branch:      None
User:        Jochen Van de Velde
Date:        2015-05-26 21:27:05+00:00
Summary:     Remove spaces around kwargs in metadata.rst

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/8016ad868acd/
Changeset:   8016ad868acd
Branch:      rel_0_9
User:        Jochen Van de Velde
Date:        2015-05-27 17:54:22+00:00
Summary:     Remove spaces around kwargs in metadata.rst

(cherry picked from commit 1bc7881171e02a80bcdb45191be6c6d83b6f01fd)

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

<< < 1 .. 15 16 17 18 19 .. 30 > >> (Page 17 of 30)