| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
Change-Id: Id0c8eb9c574c44365f6b8bca93b562dea5c8f9eb
|
| |
|
|
|
| |
rel_1_4 (#8933)
Change-Id: I7f3aa96447ade605becbdef01bc19f3b78dbd6d1
|
| |
|
|
|
|
| |
Add back pypy, python 3.12
Change-Id: Ie3b3b890d75b3939b3d5f684ec7eadadfe06a5ea
|
| |
|
|
| |
Change-Id: Iee0077f8c662da59ee63fa73296cb04ab1b09551
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Py 3.11 is released so I assume we can remove "rc" qualifiers
here
aiosqlite is causing python 3.11 crashes, so I assume this is
due to https://github.com/python/cpython/issues/99205.
I'm only guessing the syntax here, so there may be subsequent
commits if this doesnt work
Change-Id: I6f2ead3e0aca933a972efadf3891edbcdd83501c
|
| |
|
|
| |
Change-Id: Id1f13e71b803ead2cebfcca02720ab3d6504f57c
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [actions/checkout](https://github.com/actions/checkout) from 2 to 3.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](https://github.com/actions/checkout/compare/v2...v3)
---
updated-dependencies:
- dependency-name: actions/checkout
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [actions/setup-python](https://github.com/actions/setup-python) from 2 to 4.
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](https://github.com/actions/setup-python/compare/v2...v4)
---
updated-dependencies:
- dependency-name: actions/setup-python
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Restrict the GitHub token permissions only to the required ones; this way, even if the attackers will succeed in compromising your workflow, they won’t be able to do much.
- Included permissions for the action. https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions
https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions
https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs
[Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/)
Signed-off-by: naveen <172697+naveensrinivasan@users.noreply.github.com>
|
| |
|
|
| |
Change-Id: I1d399d9532bc63d00a730e3981aef79ad99a97bb
|
| |
|
|
| |
Change-Id: Iaf801a028510f276cf94b4999f129de8f4eb590c
|
| |
|
|
|
|
|
| |
the commit in 51e6a62ab371897d646a5
included a comment that appears to not be accepted
Change-Id: I1e56293e0e75c0440073bff7190b4961cfebc353
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
the most recent pypy 7.3.8 series (3.7 and 3.9 included, likely
3.8 as well) have installed a 9 year old version of SQLite,
and additionally seem to have some other behavioral changes
like formatting of exception messages that is breaking
some tests. as we are waiting on a response at [1]
remove pypy testing for now.
[1] https://foss.heptapod.net/pypy/pypy/-/issues/3690
Change-Id: I66650635111e71241b5c45a778954544c8d2490e
|
| |
|
|
|
|
| |
also drop 3.7, 3.8 from mypy GH action
Change-Id: Ib273219edf88ad66f591e044f0984bd364b395f5
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As discussed in #7589, `slotscheck` can prevent slots-related mistakes from creeping back in.
Plan for now is to have slotscheck part of the "lint" tests
(renamed from pep8) that will run for CI and github actions.
To support slotscheck's runtime nature, slotscheck is
run twice, first with cython exts enabled and then
with them disabled via new environment variable.
Also added sqlalchemy[mypy] dependency to support slots
checking the mypy plugin.
Found and fixed one more `__slots__` issue by disabling C
exts.
Closes: #7670
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/7670
Pull-request-sha: 3e77fe5449615a3c7c61ce9a1e4e79cd6636a89a
Change-Id: I90cdd284cdcee316a38856ba94d72ffc98947c5a
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Starting to set up practices and conventions to
get the library typed.
Key goals for typing are:
1. whole library can pass mypy without any strict
turned on.
2. we can incrementally turn on some strict flags on a per-package/
module basis, as here we turn on more strictness for sqlalchemy.util, exc,
and log
3. mypy ORM plugin tests work fully without sqlalchemy2-stubs
installed
4. public facing methods all have return types, major parameter
signatures filled in also
5. Foundational elements like util etc. are typed enough so that
we can use them in fully typed internals higher up the stack.
Conventions set up here:
1. we can use lots of config in setup.cfg to limit where mypy
is throwing errors and how detailed it should be in different
packages / modules. We can use this to push up gerrits
that will pass tests fully without everything being typed.
2. a new tox target pep484 is added. this links to a new jenkins
pep484 job that works across all projects (alembic, dogpile, etc.)
We've worked around some mypy bugs that will likely
be around for awhile, and also set up some core practices
for how to deal with certain things such as public_factory
modules (mypy won't accept a module from a callable at all,
so need to use simple type checking conditionals).
References: #6810
Change-Id: I80be58029896a29fd9f491aa3215422a8b705e12
|
| |
|
|
| |
Change-Id: Ib2da811acbad291dc9bbe798c84f2309f5d0f21e
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
<!-- Provide a general summary of your proposed changes in the Title field above -->
### Description
<!-- Describe your changes in detail -->
Python 3.10 was released last week.
Test on Python 3.10 and add the Trove classifier.
### Checklist
<!-- go over following points. check them with an `x` if they do apply, (they turn into clickable checkboxes once the PR is submitted, so no need to do everything at once)
-->
This pull request is:
- [ ] A documentation / typographical error fix
- Good to go, no issue or tests are needed
- [x] A short code fix
- please include the issue number, and create an issue if none exists, which
must include a complete example of the issue. one line code fixes without an
issue and demonstration will not be accepted.
- Please include: `Fixes: #<issue number>` in the commit message
- please include tests. one line code fixes without tests will not be accepted.
- [ ] A new feature implementation
- please include the issue number, and create an issue if none exists, which must
include a complete example of how the feature would look.
- Please include: `Fixes: #<issue number>` in the commit message
- please include tests.
**Have a nice day!**
^ Which checklist option should I use?
Should I do something to trigger/test all the workflows?
Closes: #7179
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/7179
Pull-request-sha: 5df7ff0e0d309301a877314e620fadb6f3f570cb
Change-Id: Ib7ecc0de75f7dffdf05db13563f7be10898e67ba
|
| |
|
|
|
|
|
| |
There are still some SQLite / MySQL specific occurrences
of "master" but this is most of it.
Change-Id: I0144c992e2f0207777e20e058b63a11c031986b9
|
| |
|
|
| |
Change-Id: I579e914e7bea38f73304f4d624649f09554ab21c
|
| |
|
|
|
| |
Fixes: #6967
Change-Id: I222cb5bdedf572e734c827d72bcbced202cdd62f
|
| |
|
|
|
|
| |
Support skipping mypy tests based on interpreter version
Change-Id: I98963318dbb2e7e097ad5518e0e4022349ca9779
|
| |
|
|
| |
Change-Id: Iaa5c3ec2ad2bf70da412cc79871d22b7ea3bf9a6
|
| |\ |
|
| | |
| |
| |
| |
| | |
Fixes: #5634
Change-Id: Ie8d4076ee35234b535a04e6fb9321096df3f648b
|
| |/
|
|
| |
Change-Id: I3b80b836ca547fa92f324acb265180cdeea17611
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
this provides a front-end option to disable tests marked
as timing_intensive, all of which are in test_pool, which are more
fragile and aren't consistent on the
github runners. also remove /reduce unnecessary time.sleep()
from two other pool tests that are not timing intensive.
note that this removes test_hanging_connect_within_overflow
from the github runs via the timing_intensive requirement.
I've also removed MockReconnectTest from exclusions as those are
really important tests and they use mocks so should not have
platform dependent issues. Need to see what the
windows failures are.
Closes: #5633
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/5633
Pull-request-sha: 166833e16ec342dfa10edb287d7aa495ddd1b59d
Change-Id: Icb3d284a2a952e2495d80fa91e22e0b32a54340f
|
| |
|
|
|
| |
Fixes: #5223
Change-Id: I0952e54ed9af2952ea340be1945311376ffc1ad2
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
**Added**:
1. ARM64 jobs in Github Workflows For Testing And Development Of Wheels
2. Two script files for creating wheels and testing.
Resolves #5436
Signed-off-by: odidev <odidev@puresoftware.com>
Co-authored-by: Federico Caselli <cfederico87@gmail.com>
Closes: #5480
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/5480
Pull-request-sha: 131ef520bbf863ad9b65ca3bf3c2d2d214405702
Change-Id: Ia10dadd93365ba4beeefbd27c060bc077c2d7aeb
|
| |
|
|
|
|
|
|
|
| |
- in create wheel set minimum versions of setuptools and wheel to avoid
failure in python 3.5 with metadata configured in setup.cfg
- update action versions
- test also cext in the pull requests
Change-Id: Iaa5e4e4000c7faa688b51f2f41428c7dd7cae9c3
|
| |
|
|
| |
Change-Id: I2e32ba315a79dcfc7c5f79ed6517ac0cee4f55e3
|
|
|
Trying the pr to check if it works right away
### Description
<!-- Describe your changes in detail -->
### Checklist
<!-- go over following points. check them with an `x` if they do apply, (they turn into clickable checkboxes once the PR is submitted, so no need to do everything at once)
-->
This pull request is:
- [ ] A documentation / typographical error fix
- Good to go, no issue or tests are needed
- [x] A short code fix
- please include the issue number, and create an issue if none exists, which
must include a complete example of the issue. one line code fixes without an
issue and demonstration will not be accepted.
- Please include: `Fixes: #<issue number>` in the commit message
- please include tests. one line code fixes without tests will not be accepted.
- [ ] A new feature implementation
- please include the issue number, and create an issue if none exists, which must
include a complete example of how the feature would look.
- Please include: `Fixes: #<issue number>` in the commit message
- please include tests.
**Have a nice day!**
Closes: #5222
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/5222
Pull-request-sha: afbb8567525f3841554d3ba599ef4d713c78e647
Change-Id: I4981b02f900e76e446cf42e6cc6495ffc0883951
|