Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version 1? #186

Closed
samuelcolvin opened this issue Sep 11, 2022 · 3 comments · Fixed by #309
Closed

Version 1? #186

samuelcolvin opened this issue Sep 11, 2022 · 3 comments · Fixed by #309

Comments

@samuelcolvin
Copy link
Owner

I think watchfiles is pretty stable and we should release version 1.

Unless anyone has any problems with that, or urgent bugs to fix/features to add; I'll release v1.0.0b1 in about a week.

@samuelcolvin samuelcolvin pinned this issue Sep 12, 2022
@samuelcolvin samuelcolvin changed the title Version 1 Version 1? Sep 12, 2022
@samuelcolvin
Copy link
Owner Author

samuelcolvin commented Sep 16, 2022

Wait for:

@pradyunsg
Copy link

Unless anyone has any problems with that, or urgent bugs to fix/features to add; I'll release v1.0.0b1 in about a week.

Hi there @samuelcolvin! Would you consider making a non-0ver release?

sscherfke added a commit to sscherfke/nicegui that referenced this issue Feb 3, 2024
- The "^" specifier is often too restrictive for 0.* versions so I would
  not recommend to use it in these cases:
  https://python-poetry.org/docs/dependency-specification/
- Markdown2: The issue from 2.4.11 was fixed in 2.4.12:
  - zauberzeug#2154
  - trentm/python-markdown2#546
  - https://github.com/trentm/python-markdown2/blob/master/CHANGES.md#python-markdown2-2412
- Watchfiles: Doesn't look like v1 will introduce breaking changes:
  samuelcolvin/watchfiles#186
- python-multipart: "^0.06" is "==0.0.6" which is too strict and
  at this stage, any release can potentially add breaking changes
- aiofiles: Uses CalVer and 24.0.0 is as likely to introduce breaking
  changes as 23.2.0.
- httpx: It does not look like 1.0.0 will introduce breaking changes
  (if you already fixed any deprecation warnings).  Testing against the
  1.0.0beata0 is advisable, though.
  encode/httpx#3069
- ifaddr: Development is rather slow, package looks quite stable.
  I don't think that a 0.3.0 will add breaking changes and a 1.0 is not
  in sight.
- pytest-asyncio: Restriction to >=0.19,<0.20 seems unwanted and updates
  are needed for recent pytest versions
- pytest: Has there been a reason to not support pytest7?  pytest8
  currently breaks some plugins, but this should be fixed soon.

Fixes: zauberzeug#2485
@samuelcolvin
Copy link
Owner Author

This is done, see #309.

Sorry for the delay @pradyunsg.

@samuelcolvin samuelcolvin unpinned this issue Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants