Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
erp5
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Labels
Merge Requests
141
Merge Requests
141
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Jobs
Commits
Open sidebar
nexedi
erp5
Commits
48bd8fa6
Commit
48bd8fa6
authored
1 year ago
by
Jérome Perrin
Committed by
Arnaud Fontaine
7 months ago
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Formulator: stop trying to catch string exception
This was for Zope 2.7 and is invalid on py3
parent
d1b602c4
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
3 deletions
+1
-3
product/Formulator/Validator.py
product/Formulator/Validator.py
+1
-3
No files found.
product/Formulator/Validator.py
View file @
48bd8fa6
...
@@ -863,9 +863,7 @@ class DateTimeValidator(Validator):
...
@@ -863,9 +863,7 @@ class DateTimeValidator(Validator):
int
(
day
),
int
(
day
),
hour
,
hour
,
minute
,
timezone
))
minute
,
timezone
))
# ugh, a host of string based exceptions (not since Zope 2.7)
except
(
DateError
,
TimeError
):
except
(
'DateTimeError'
,
'Invalid Date Components'
,
'TimeError'
,
DateError
,
TimeError
)
:
self
.
raise_error
(
'not_datetime'
,
field
)
self
.
raise_error
(
'not_datetime'
,
field
)
# pass value through request in order to be restored in case if validation fail
# pass value through request in order to be restored in case if validation fail
if
getattr
(
REQUEST
,
'form'
,
None
):
if
getattr
(
REQUEST
,
'form'
,
None
):
...
...
This diff is collapsed.
Click to expand it.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment