Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
py-heptapod
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
heptapod
py-heptapod
Commits
e112c497
Commit
e112c497
authored
4 years ago
by
Georges Racinet
Browse files
Options
Downloads
Patches
Plain Diff
README: update Python version compatibility statement
That was long overdue
parent
23bd89e7
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+8
-5
8 additions, 5 deletions
README.md
with
8 additions
and
5 deletions
README.md
+
8
−
5
View file @
e112c497
...
...
@@ -23,6 +23,5 @@
1.
0.0 (for Heptapod 0.17), we are planning to follow
[
semver
](
https://semver.org
)
rules (with PEP 440 for development versions).
This package is for now Python 2 only, meaning in particular that Python 3
utilities, such as the migration scripts are not hosted here yet.
Python 3 is fully supported since version 0.13.0, tested with 3.7 and 3.8.
...
...
@@ -28,7 +27,11 @@
We will migrate to Python 3 in one shot when Mercurial and hg-git do.
[
Python 2 support is deprecated
](
https://foss.heptapod.net/heptapod/heptapod/-/issues/353
)
as of version 1.0.0. Only the
`testhelpers`
subpackage is fully supported for both Python versions,
because it can be used for more general Mercurial related testing.
Python 2 support will be dropped entirely when we will have a new home for
`testhelpers`
.
## Development guide
### Launching the tests
...
...
@@ -30,8 +33,8 @@
## Development guide
### Launching the tests
We have unit tests with
`py.test`
, they'd be typically run in a virtualenv
.
We have unit tests with
`py.test`
, they'd be typically run in a virtualenv
:
```
...
...
@@ -36,6 +39,6 @@
```
virtualenv -p python2
venv
python 3 -m venv
venv
venv/bin/pip install -r install-requirements.txt -r test-requirements.txt
venv/bin/pytest
```
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment